Result:
found more than 567 distributions - search limited to the first 2001 files matching your query
( run in 0.452 )
App-BCVI
view release on metacpan or search on metacpan
$class->register_option(
name => 'reuse-auth',
summary => "don't generate a new auth key on listener startup",
description => <<'END_POD'
A new (random) authorisation key is generated when the listener process is
started - this will invalidate the keys in use by existing SSH sessions.
This option is for use when it is necessary to restart the listener process
without invalidating client keys.
END_POD
);
my($self) = @_;
$self->send_response(100);
my $req = $self->collect_headers();
$self->DEBUG("Calling host: " . $self->calling_host) if $self->calling_host;
$self->validate_auth_key($req->{auth_key})
or $self->exit_response(900);
$self->DEBUG("Received command: $req->{command}");
my $method = $self->command_handler($req->{command})
or $self->exit_response(910);
$self->DEBUG("Dispatching to: $method");
$self->$method();
$self->send_response(200);
}
sub validate_auth_key {
my($self, $key) = @_;
return 1 if $key && $key eq $self->auth_key;
my $alias = $self->calling_host();
$self->DEBUG("Invalid Auth-Key in request from $alias") if $key;
App-BPOMUtils-NutritionFacts
view release on metacpan or search on metacpan
script/bpom-show-nutrition-facts view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
biotin (see --biotin)
biotin_nufact (see --biotin-nufact)
App-BPOMUtils
view release on metacpan or search on metacpan
script/bpom-show-nutrition-facts view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
browser (see --browser)
carbohydrate (see --carbohydrate)
App-BackupPlan
view release on metacpan or search on metacpan
lib/App/BackupPlan.pm view on Meta::CPAN
sub run {
my ($self,$now) = @_;
$now = time unless defined $now;
#validate the config file
die "App::BackupPlan configuration file is required, but was not given!" unless defined $self->{config};
#logging config
if (defined $self->{log}) {
Log::Log4perl::init($self->{log});
App-BashHistoryUtils
view release on metacpan or search on metacpan
script/delete-bash-history-entries view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
format (see --format)
histfile (see --histfile)
App-Basis-Queue
view release on metacpan or search on metacpan
bin/qpubsub view on Meta::CPAN
PEEK_DEFAULT,
'type|t=s' => {
desc => 'Type of the queue, one of ' . join( ", ", @queue_types ),
default => 'task',
required => 1,
validate => sub {
my $t = shift ;
grep {/$t/} @queue_types ;
},
},
'listen|l' =>
App-Basis
view release on metacpan or search on metacpan
lib/App/Basis.pm view on Meta::CPAN
# ----------------------------------------------------------------------------
# check that the option structure does not have repeated things in it
# returns string of any issue
sub _validate_options
{
my ($options) = @_ ;
my %seen ;
my $result = "" ;
lib/App/Basis.pm view on Meta::CPAN
# add help text for 'help' first.
$_app_simple_help_options .= sprintf $help_fmt, $dnames{'help|h|?'},
'Show help' ;
#
my $msg = _validate_options( $args{options} ) ;
if ($msg) {
die "$msg" ;
}
# get options and their descriptions
lib/App/Basis.pm view on Meta::CPAN
# possible options that can be passed
# depends => '',
# default => '',
# required => 0,
# validate => sub {}
} ;
}
# save the option string too
$full_options{$name}->{options} = $o ;
lib/App/Basis.pm view on Meta::CPAN
$_cmd_line_options{$name} = $full_options{$name}->{default}
if ( !$_cmd_line_options{$name} ) ;
}
# call the validation routine if we have one
if ( $_cmd_line_options{$name} && $full_options{$name}->{validate} ) {
die "need to pass a coderef to validate for option '$name'"
if ( !ref( $full_options{$name}->{validate} ) eq 'CODE' ) ;
die
"Option '$name' has validate and should either also have a default or be required"
if (
!( $full_options{$name}->{required}
|| $full_options{$name}->{default}
)
) ;
my $coderef = $full_options{$name}->{validate} ;
my $result = $coderef->( $_cmd_line_options{$name} ) ;
show_usage("Option '$name' does not pass validation")
if ( !$result ) ;
}
}
lib/App/Basis.pm view on Meta::CPAN
desc => 'local system location of xml data'
, required => 1
}
, 'url|u=s' => {
desc => 'where to find xml data on the internet'
, validate => sub { my $url = shift ; return $url =~ m{^(http|file|ftp)://} ; }
}
, 'keep|k' => {
# no point in having this if there is no file option
desc => 'keep the local file, do not rename it'
, depends => 'file'
lib/App/Basis.pm view on Meta::CPAN
complex way, more features, validation, dependancies etc
'fred|f=s' => {
desc => 'description of argument',
# check if fred is one of the allowed things
validate => sub { my $fred = shift ; $fred =~ m/bill|mary|jane|sam/i ;},
# does this option need another option to exist
depends => 'otheroption'
}
'fred|f=s' => {
desc => 'description of argument',
App-BencherUtils
view release on metacpan or search on metacpan
script/bencher-code view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
codes (see --code)
format (see --format)
App-BookmarkFeed
view release on metacpan or search on metacpan
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
App-BorgRestore
view release on metacpan or search on metacpan
lib/App/BorgRestore/PathTimeTable/DB.pm view on Meta::CPAN
Data is written to the database directly and existing data is updated where necessary.
For performance reasons this class keeps an internal cache so that the database
is only contacted when necessary. The cache assumes that the path are sorted so
that all files from one directory are added, before files from another. If a
path from a different directory is added, the previous cache is invalidated.
Upon invalidation the time stamp is written to the database. If paths are
properly sorted, this results in only a single database write for each path.
=cut
lib/App/BorgRestore/PathTimeTable/DB.pm view on Meta::CPAN
method add_path($path, $time) {
$log->tracef("Adding path to cache: %s", $path) if TRACE;
$self->{stats}->{total_paths}++;
my $old_cache_path = $self->{current_path_in_cache};
# Check if the new path requires us to (partially) invalidate our cache and
# add any files/directories to the database. If the new path is a subpath
# (substring actually) of the cached path, we can keep it only in the cache
# and no flush is needed. Otherwise we need to flush all parts of the path
# that are no longer contained in the new path.
#
App-BraveUtils
view release on metacpan or search on metacpan
script/restart-brave view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
format (see --format)
log_level (see --log-level)
App-BrowserUtils
view release on metacpan or search on metacpan
script/restart-browsers view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
chrome_cmd (see --chrome-cmd)
firefox_cmd (see --firefox-cmd)
App-CELL
view release on metacpan or search on metacpan
lib/App/CELL.pm view on Meta::CPAN
=cut
sub load {
my $class = shift;
my ( %ARGS ) = validate( @_, {
enviro => { type => SCALAR, optional => 1 },
sitedir => { type => SCALAR, optional => 1 },
verbose => { type => SCALAR, default => 0 },
} );
my $status;
App-CMAM
view release on metacpan or search on metacpan
inc/Module/Install/Metadata.pm view on Meta::CPAN
);
while ( my ($pattern, $license, $osi) = splice(@phrases, 0, 3) ) {
$pattern =~ s{\s+}{\\s+}g;
if ( $license_text =~ /\b$pattern\b/i ) {
if ( $osi and $license_text =~ /All rights reserved/i ) {
print "WARNING: 'All rights reserved' in copyright may invalidate Open Source license.\n";
}
$self->license($license);
return 1;
}
}
App-CPAN-Changes
view release on metacpan or search on metacpan
script/cpan-changes view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
=head2 Common for all subcommands
App-CPANMetaUtils
view release on metacpan or search on metacpan
lib/App/CPANMetaUtils.pm view on Meta::CPAN
=item * L<convert-cpan-meta>
=item * L<gen-cpan-meta>
=item * L<validate-cpan-meta>
=back
=head1 HOMEPAGE
App-CSVUtils
view release on metacpan or search on metacpan
lib/App/CSVUtils/csv_check_cell_values.pm view on Meta::CPAN
quiet => {
schema => 'bool*',
cmdline_aliases => {q=>{}},
},
print_validated => {
summary => 'Print the validated values of each cell',
schema => 'bool*',
description => <<'_',
When validating with schema, will print each validated (possible coerced,
filtered) value of each cell.
_
},
},
lib/App/CSVUtils/csv_check_cell_values.pm view on Meta::CPAN
}
for my $idx (@{ $r->{selected_fields_idx_array_sorted} }) {
my $res = $r->{code}->( $r->{input_row}[$idx] );
if ($res->[0]) {
my $msg = "Row #$r->{input_data_rownum} field '$r->{input_fields}[$idx]': Value '$r->{input_row}[$idx]' does NOT validate: $res->[0]";
$r->{result} = [400, $msg, $r->{util_args}{quiet} ? undef : $msg];
$r->{wants_skip_files}++;
} else {
if ($r->{util_args}{print_validated}) {
print $res->[1], "\n";
}
}
}
},
after_close_input_files => sub {
my $r = shift;
$r->{result} //= [200, "OK", $r->{util_args}{quiet} ? undef : "All cells validate"];
},
);
1;
# ABSTRACT: Check the value of single cells of CSV against code/schema/regex
lib/App/CSVUtils/csv_check_cell_values.pm view on Meta::CPAN
Overriden by C<--input-sep-char>, C<--input-quote-char>, C<--input-escape-char>
options. If one of those options is specified, then C<--input-tsv> will be
ignored.
=item * B<print_validated> => I<bool>
Print the validated values of each cell.
When validating with schema, will print each validated (possible coerced,
filtered) value of each cell.
=item * B<quiet> => I<bool>
(No description)
App-CalId
view release on metacpan or search on metacpan
lib/App/CalId.pm view on Meta::CPAN
},
time_zone => {
schema => 'str*',
},
},
"x.perinci.sub.wrapper.disable_validate_args" => 1,
result_naked => 1,
};
sub gen_monthly_calendar {
my %args = @_;
my $m = $args{month};
lib/App/CalId.pm view on Meta::CPAN
},
time_zone => {
schema => 'str*',
},
},
"x.perinci.sub.wrapper.disable_validate_args" => 1,
};
sub gen_calendar {
my %args = @_;
my $y = $args{year};
my $m = $args{month};
App-CalcAccumulatedDiscounts
view release on metacpan or search on metacpan
script/calc-accumulated-discounts view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
discounts (see --discounts)
format (see --format)
App-CalcAccumulatedInflation
view release on metacpan or search on metacpan
script/calc-accumulated-inflation view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
base_index (see --base-index)
base_year (see --base-year)
App-CamelPKI
view release on metacpan or search on metacpan
lib/App/CamelPKI/SysV/Apache.pm view on Meta::CPAN
is($response->code, 404, "500 would be bad") or
diag $response->content;
unlike($webserver->tail_error_logfile,
qr/certificate signature failure/, <<"EXPLANATION");
``certificate signature failure'' is the message one gets when mod_ssl
attempts to validate a certificate whose hash algorithm it doesn't
know about.
EXPLANATION
}
my $sha256directory = fresh_directory;
App-CekBpom
view release on metacpan or search on metacpan
script/cek-bpom-products view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
format (see --format)
get_product_detail (see --get-product-detail)
App-Changelord
view release on metacpan or search on metacpan
lib/App/Changelord.pm view on Meta::CPAN
parent_command => $self,
)->run;
}
subcommand $_ => 'App::Changelord::Command::' . ucfirst $_ =~ s/-(.)/uc $1/er
for qw/ schema validate version bump init add git-gather print /;
1;
__END__
App-Chart
view release on metacpan or search on metacpan
lib/App/Chart.pm view on Meta::CPAN
return undef;
}
sub setup_source_help {
my ($pred, $node) = @_;
require App::Chart::Sympred;
App::Chart::Sympred::validate ($pred);
# newer get higher priority
unshift @source_help_list, [ $pred, $node ];
}
App-Cheats
view release on metacpan or search on metacpan
curl --head www.google.com
# Check if website/URL is up (Jira,ping)
curl -s --head http://localhost:8081/secure/Dashboard.jspa | head -1
# Download files using curl and validate the checksum:
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert"
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert.sha256"
echo "$(cat kubectl-convert.sha256) kubectl-convert" | sha256sum --check
#
# Install the new command.
child.addEventListener("click", second);
parent.addEventListener("click", first, true);
when clicking child element, first method will be called before second.
# Add a function to an event (HTML Event Listener)
is_no_automatic_change.addEventListener("change", validate_general_tab_checks);
document.querySelector("input[name=NAME]").addEventListener("change", myFunc)
# Remove a function from an event (HTML Event Listener)
document.querySelector("input[name=NAME]").removeEventListener("change", myFunc, false)
#############################################################
## Perl Modules - Business::CreditCard
#############################################################
# Validate a credit card number.
perl -MBusiness::CreditCard -E 'say validate("5276 4400 6542 1319")'
1
#
perl -MBusiness::CreditCard -E 'say cardtype("5276 4400 6542 1319")'
MasterCard
#############################################################
# Modern::Perl defaults to v5.12 (bug!?)
perl -E 'say $^V'
v5.36.0
perl -Modern::Perl -e 'say Modern::Perl::validate_date(2022)'
:5.34
perl -Modern::Perl -e 'say Modern::Perl::validate_date()'
:5.12
perl -E 'sub abc ($n) {$n}'
perl -Modern::Perl=2022 -e 'sub abc ($n) {$n}'
perl -Modern::Perl -e 'sub abc ($n) {$n}'
Illegal character in prototype for main::abc : $n at -e line 1.
# Notebook example 6. multiple pages/tabs (PTk)
perl -MTk -MTk::NoteBook -le '$nb=MainWindow->new->NoteBook->pack; $nb->add("page0$_", -label => "Page $_") for 1..5; @pgs = map $nb->page_widget($_), $nb->pages; ($p,@rest)=@pgs; $nb1=$p->NoteBook->pack; $nb1->add("page1$_", -label => "Page $_") for...
# Entry widget validation options (PTk)
perl -MTk -le 'MainWindow->new->Entry(-validate => "key", -validatecommand => sub{$_[1] =~ /\d/}, -invalidcommand => sub{ print "ERROR" })->pack->focus; MainLoop'
# Making Scrollbars (PTk)
# When text widget is scrolled its "-yscrollcommand" command is invoked. This calls $s->set(...)
# When the scrollbar is clicked on "-command" is invoked which calls $t->yview(...)
perl -MTk -le '$mw=MainWindow->new; $s=$mw->Scrollbar; $t=$mw->Text(-yscrollcommand => ["set" => $s]); $s->configure(-command => ["yview" => $t]); $s->pack(-side => "right", -fill => "y"); $t->pack(-fill => "both"); MainLoop'
App-ChromeUtils
view release on metacpan or search on metacpan
script/restart-chrome view on Meta::CPAN
You can also put configuration for multiple programs inside a single file, and use filter C<program=NAME> in section names, e.g. C<[program=NAME ...]> or C<[SOMESECTION program=NAME]>. The section will then only be used when the reading program match...
You can also filter a section by environment variable using the filter C<env=CONDITION> in section names. For example if you only want a section to be read if a certain environment variable is true: C<[env=SOMEVAR ...]> or C<[SOMESECTION env=SOMEVAR ...
To load and configure plugins, you can use either the C<-plugins> parameter (e.g. C<< -plugins=DumpArgs >> or C<< -plugins=DumpArgs@before_validate_args >>), or use the C<[plugin=NAME ...]> sections, for example:
[plugin=DumpArgs]
-event=before_validate_args
-prio=99
[plugin=Foo]
-event=after_validate_args
arg1=val1
arg2=val2
which is equivalent to setting C<< -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2 >>.
List of available configuration parameters:
chrome_cmd (see --chrome-cmd)
format (see --format)
App-Chronicle
view release on metacpan or search on metacpan
5.1.2 - 2nd January 2016
* Load gravitars in a protocol-agnostic fashion.
5.1.1 - 4th July 2015
* Updated default RSS-feed to validate correctly.
5.1.0 - 16th June 2015
* Allow per-post templates.
* Allow posts to be truncated.
* Allow user to configure the man/max/step-size of the tag-cloud.
App-Cinema
view release on metacpan or search on metacpan
lib/App/Cinema/Controller/Comment.pm view on Meta::CPAN
$c->res->redirect( $c->uri_for('/menu/about') );
return 0;
}
my $form = $self->formbuilder;
my $comment = $form->field('desc');
if ( $form->submitted && $form->validate ) {
if ( $form->submitted eq 'Preview' ) {
$c->stash->{message} = $comment;
}
elsif ( $form->submitted eq 'Save' ) {
$c->model('MD::Comment')->create(
App-ClusterSSH
view release on metacpan or search on metacpan
lib/App/ClusterSSH/Config.pm view on Meta::CPAN
$self->{title} = uc($Script);
$clusters = App::ClusterSSH::Cluster->new();
return $self->validate_args(%args);
}
sub validate_args {
my ( $self, %args ) = @_;
my @unknown_config = ();
foreach my $config ( sort( keys(%args) ) ) {
lib/App/ClusterSSH/Config.pm view on Meta::CPAN
# tidy up entries, just in case
$read_config{terminal_font} =~ s/['"]//g
if ( $read_config{terminal_font} );
$self->validate_args(%read_config);
}
sub load_configs {
my ( $self, @configs ) = @_;
lib/App/ClusterSSH/Config.pm view on Meta::CPAN
=item $config->parse_config_file('<filename>');
Read in configuration from given filename
=item $config->validate_args();
Validate and apply all configuration loaded at this point
=item $path = $config->search_dirs('<name>', @seaarch_directories);
App-Cmd
view release on metacpan or search on metacpan
lib/App/Cmd.pm view on Meta::CPAN
#pod [ "blortex|X", "use the blortex algorithm" ],
#pod [ "recheck|r", "recheck all results" ],
#pod );
#pod }
#pod
#pod sub validate_args {
#pod my ($self, $opt, $args) = @_;
#pod
#pod # no args allowed but options!
#pod $self->usage_error("No args allowed") if @$args;
#pod }
lib/App/Cmd.pm view on Meta::CPAN
#pod =method execute_command
#pod
#pod $app->execute_command($cmd, \%opt, @args);
#pod
#pod This method will invoke C<validate_args> and then C<run> on C<$cmd>.
#pod
#pod =cut
sub execute_command {
my ($self, $cmd, $opt, @args) = @_;
local our $active_cmd = $cmd;
$cmd->validate_args($opt, \@args);
$cmd->execute($opt, \@args);
}
#pod =method plugin_search_path
#pod
lib/App/Cmd.pm view on Meta::CPAN
#pod =method usage_error
#pod
#pod $self->usage_error("Something's wrong!");
#pod
#pod Used to die with nice usage output, during C<validate_args>.
#pod
#pod =cut
sub usage_error {
my ($self, $error) = @_;
lib/App/Cmd.pm view on Meta::CPAN
[ "blortex|X", "use the blortex algorithm" ],
[ "recheck|r", "recheck all results" ],
);
}
sub validate_args {
my ($self, $opt, $args) = @_;
# no args allowed but options!
$self->usage_error("No args allowed") if @$args;
}
lib/App/Cmd.pm view on Meta::CPAN
=head2 execute_command
$app->execute_command($cmd, \%opt, @args);
This method will invoke C<validate_args> and then C<run> on C<$cmd>.
=head2 plugin_search_path
This method returns the plugin_search_path as set. The default implementation,
if called on "YourApp::Cmd" will return "YourApp::Cmd::Command"
lib/App/Cmd.pm view on Meta::CPAN
=head2 usage_error
$self->usage_error("Something's wrong!");
Used to die with nice usage output, during C<validate_args>.
=head1 TODO
=over 4
( run in 0.452 second using v1.01-cache-2.11-cpan-a5abf4f5562 )