App-PickRandomLines
view release on metacpan or search on metacpan
script/pick view on Meta::CPAN
#!perl
### begin code_after_shebang
# Note: This script is a CLI for Riap function /App/PickRandomLines/pick_random_lines
# and generated automatically using Perinci::CmdLine::Gen version 0.502
### end code_after_shebang
# PERICMD_INLINE_SCRIPT: {"code_after_shebang":"...","config_dirs":null,"config_filename":"pick.conf","env_name":"PICK_OPT","include":null,"log":null,"pack_deps":1,"pod":0,"read_config":1,"read_env":1,"script_name":"pick","script_summary":"Pick one o...
# This script is generated by Perinci::CmdLine::Inline version 0.554 on Mon Nov 20 12:11:15 2023.
# Rinci metadata taken from these modules: App::PickRandomLines (no version)
# You probably should not manually edit this file.
## no critic: TestingAndDebugging::RequireUseStrict
# PODNAME: pick
script/pick view on Meta::CPAN
All found files will be read and merged.
To disable searching for configuration files, pass C<--no-config>.
You can put multiple profiles in a single file by using section names like C<[profile=SOMENAME]> or C<[SOMESECTION profile=SOMENAME]>. Those sections will only be read if you specify the matching C<--config-profile SOMENAME>.
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:
algorithm (see --algorithm)
files (see --file)
format (see --format)
naked_res (see --naked-res)
num_lines (see --num-lines)
=head1 ENVIRONMENT
script/pick view on Meta::CPAN
#
#sub _install_methods {
# my ($me, $to, $role) = @_;
#
# my $methods = $me->_concrete_methods_of($role);
#
# my %existing_methods;
# @existing_methods{keys %{ $me->_all_subs($to) }} = ();
#
# # _concrete_methods_of caches its result on roles. that cache needs to be
# # invalidated after applying roles
# delete $INFO{$to}{methods} if $INFO{$to};
#
# foreach my $i (keys %$methods) {
# next
# if exists $existing_methods{$i};
#
# my $glob = _getglob "${to}::${i}";
# *$glob = $methods->{$i};
#
# # overloads using method names have the method stored in the scalar slot
script/pick view on Meta::CPAN
#
# use Data::Sah qw(gen_validator);
# my $validator = gen_validator("rinci::function_meta*");
# say $validator->($data) ? "valid" : "INVALID!";
#
# # Data::Sah can also create validator that returns nice error message string
# # and/or coerced value. Data::Sah can even create validator that targets other
# # language, like JavaScript. All from the same schema. See its documentation
# # for more details.
#
#To validate function parameters against this schema (requires L<Params::Sah>):
#
# use Params::Sah qw(gen_validator);
#
# sub myfunc {
# my @args = @_;
# state $validator = gen_validator("rinci::function_meta*");
# $validator->(\@args);
# ...
# }
#
script/pick-random-lines view on Meta::CPAN
#!perl
### begin code_after_shebang
# Note: This script is a CLI for Riap function /App/PickRandomLines/pick_random_lines
# and generated automatically using Perinci::CmdLine::Gen version 0.502
### end code_after_shebang
# PERICMD_INLINE_SCRIPT: {"code_after_shebang":"...","config_dirs":null,"config_filename":"pick-random-lines.conf","env_name":"PICK_RANDOM_LINES_OPT","include":null,"log":null,"pack_deps":1,"pod":0,"read_config":1,"read_env":1,"script_name":"pick-ran...
# This script is generated by Perinci::CmdLine::Inline version 0.554 on Mon Nov 20 12:11:10 2023.
# Rinci metadata taken from these modules: App::PickRandomLines (no version)
# You probably should not manually edit this file.
## no critic: TestingAndDebugging::RequireUseStrict
# PODNAME: pick-random-lines
script/pick-random-lines view on Meta::CPAN
All found files will be read and merged.
To disable searching for configuration files, pass C<--no-config>.
You can put multiple profiles in a single file by using section names like C<[profile=SOMENAME]> or C<[SOMESECTION profile=SOMENAME]>. Those sections will only be read if you specify the matching C<--config-profile SOMENAME>.
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:
algorithm (see --algorithm)
files (see --file)
format (see --format)
naked_res (see --naked-res)
num_lines (see --num-lines)
=head1 ENVIRONMENT
script/pick-random-lines view on Meta::CPAN
#
#sub _install_methods {
# my ($me, $to, $role) = @_;
#
# my $methods = $me->_concrete_methods_of($role);
#
# my %existing_methods;
# @existing_methods{keys %{ $me->_all_subs($to) }} = ();
#
# # _concrete_methods_of caches its result on roles. that cache needs to be
# # invalidated after applying roles
# delete $INFO{$to}{methods} if $INFO{$to};
#
# foreach my $i (keys %$methods) {
# next
# if exists $existing_methods{$i};
#
# my $glob = _getglob "${to}::${i}";
# *$glob = $methods->{$i};
#
# # overloads using method names have the method stored in the scalar slot
script/pick-random-lines view on Meta::CPAN
#
# use Data::Sah qw(gen_validator);
# my $validator = gen_validator("rinci::function_meta*");
# say $validator->($data) ? "valid" : "INVALID!";
#
# # Data::Sah can also create validator that returns nice error message string
# # and/or coerced value. Data::Sah can even create validator that targets other
# # language, like JavaScript. All from the same schema. See its documentation
# # for more details.
#
#To validate function parameters against this schema (requires L<Params::Sah>):
#
# use Params::Sah qw(gen_validator);
#
# sub myfunc {
# my @args = @_;
# state $validator = gen_validator("rinci::function_meta*");
# $validator->(\@args);
# ...
# }
#
( run in 0.590 second using v1.01-cache-2.11-cpan-a5abf4f5562 )