view release on metacpan or search on metacpan
script/riap view on Meta::CPAN
Number of seconds to cache Riap results from server, to speed up things like tab
completion.
=head1 FAQ
=head2 The prompt looks rather garbled (e.g. extra " m >" character)!
It looks to be an issue with L<Term::ReadLine::Perl>. Try installing
L<Term::ReadLine::Gnu> instead.
=head2 How do I redirect output to files?
B<riap> is meant to be a simple shell, not a full-blown Unix shell. Besides, a
view release on metacpan or search on metacpan
corpus/generate_scripts.pl view on Meta::CPAN
# FindBin::Bin is a dir, so set $no_file to true for reliability
my ($vol, $dirs, $file) = splitpath($FindBin::Bin, 1);
my @base = splitdir($dirs);
my @inc;
# this looks more complicated than it really is
my $bin = pop @base;
# ./lib
my @sets = [ [$bin, qw(lib)] ];
view release on metacpan or search on metacpan
=item profile
This is a configuration file which collects options that you always need
to specifiy. The keys of the hash are option names while the values are,
well, corresponding values. A typical profile looks like:
{db => '<file>',
build => '<file>',
ign => '<file>',
pool => '<dir>',
Adopt all the orphans, binary packages of them and their entries in the
reference counting database will all be removed, there will be no sign
that they ever existed once this command finishes. A typical pattern would be:
# Module A::B::C looks interesting, install it and have a try.
$ rs install A::B::C
# Don't want it anymore.
$ rs uninstall A::B::C
view release on metacpan or search on metacpan
script stops. You can either move or delete the directory
and start again.
=item * Look for template files
The program looks in F<.scriptdistrc> for files to copy into
the target script distribution directory. After that, it
adds more files unless they already exist (i.e. the script
found them in the template directory). The script replaces
strings matching C<%%SCRIPTDIST_FOO%%> with the internal
value of FOO. The defined values are currently SCRIPT, which
view release on metacpan or search on metacpan
script/sdif view on Meta::CPAN
=item B<-V>, B<--parallel>
=item B<-V3>, B<--parallel=3>
B<sdif> processes only looks-like-diff-output data and print anything
else as is to standard out. Option C<-V> or C<--parallel> makes
unknown text as common to old and new data. This is useful to see
file including conflict marker data compatible with L<git(1)>.
This option takes an optional number parameter and 2 is assumed when
view release on metacpan or search on metacpan
lib/App/sdview/Output/Formatted.pm view on Meta::CPAN
my @lines = $text->split( qr/\n/ );
@lines or @lines = ( String::Tagged->new ) if defined $leader;
# If there's a background set, then space-pad every line to the same width
# so it looks neater on the terminal
# https://rt.cpan.org/Ticket/Display.html?id=140536
if( defined $typestyle{bg} ) {
my $width = max map { length $_ } @lines;
$_ .= " " x ( $width - length $_ ) for @lines;
}
view release on metacpan or search on metacpan
lib/App/starbucksloginator.pm view on Meta::CPAN
my ( $connected, $response );
( $connected, $response ) = $self->try_to_get_out;
if ( $connected ) {
say "It looks like you can already get out -- Cancelling login";
exit 0;
}
else {
say "Unable to get out -- Attempting to login";
}
view release on metacpan or search on metacpan
script/tchart view on Meta::CPAN
use strict;
use warnings;
#use App::chart;
use Getopt::Long qw(:config no_ignore_case bundling);
use Scalar::Util qw(looks_like_number);
our $AUTHORITY = 'cpan:PERLANCAR'; # AUTHORITY
our $DATE = '2024-02-06'; # DATE
our $DIST = 'App-tchart'; # DIST
our $VERSION = '0.062'; # VERSION
script/tchart view on Meta::CPAN
my @lines = <>;
my $fmt = $Opts{input};
if (!$fmt) {
if (looks_like_number($lines[0]) || $lines[0] =~ /\t/) {
$fmt = "tsv";
} else {
$fmt = "json";
}
}
view release on metacpan or search on metacpan
lib/App/td.pm view on Meta::CPAN
my $sums = [map {0} @$cols];
for my $i (0..$#{$rows_as_aoaos}) {
my $row = $rows_as_aoaos->[$i];
for my $j (0..@$cols-1) {
$sums->[$j] += $row->[$j]
if Scalar::Util::looks_like_number($row->[$j]);
}
}
my $avgs;
my $results;
if ($action =~ /avg/) {
view release on metacpan or search on metacpan
Use ANSI-colors for the I<pretty> layout. Defaults to true.
=item display_layout
In which format to display your timeline. I<txtnix> defines two different
layout: I<simple> is a line oriented very basic layout. I<pretty> looks
less dense and supports ANSI colors and text wrapping. Defaults to simple.
=item wrap_text
If to wrap text in pretty display. Defaults to true.
view release on metacpan or search on metacpan
script/ucpan view on Meta::CPAN
=over 2
=item * L<cpanm> can take more than one mirror, but L<cpan-outdated> only enables last one.
=item * L<cpan-outdated> only looks at the modules list of the mirror looking for outdated modules. It does not reference metacpan's database like L<cpanm>.
=back
=item --configure-timeout
view release on metacpan or search on metacpan
t/lib/cmd/subject/recipe.t view on Meta::CPAN
verb => 'load',
params => [ $fname ],
);
my $new = $cmd->execute->recipe;
isa_ok $new, 'App::vaporcalc::Recipe';
ok $new->target_pg == 65, 'loaded recipe looks ok';
};
done_testing
view release on metacpan or search on metacpan
# ROX puts all of its windows in the same group, so they open
# with the same tags. Disable grouping for ROX Filer.
/^ROX-Filer:/ group=0
# Chrome looks best without titlebars IMO, also allow activation.
/Google Chrome|Chromium/ titleless=on allow=+activate
view release on metacpan or search on metacpan
script/_wordlist view on Meta::CPAN
#
#=head2 COMPLETE_BASH_SUMMARY_ALIGN
#
#String. Either C<left> (the default) or C<right>.
#
#The C<left> align looks something like this:
#
# --bar Summary about the bar option
# --baz Summary about the baz option
# --foo Summary about the foo option
# --schapen Summary about the schapen option
script/_wordlist view on Meta::CPAN
# for (@_) {
# my $ref = ref($_);
# if ($ref eq 'ARRAY') { $prev = $_ }
# elsif ($ref eq 'HASH') { $meta = $_ }
# elsif (!$ref) {
# if (Scalar::Util::looks_like_number($_)) {
# $status = $_;
# } else {
# $msg = $_;
# }
# }
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
t/01-options.t view on Meta::CPAN
my $version= `$XML_GREP2 -V 1 2>&1`;
chomp $version;
like( `$XML_GREP2 -V 1 2>&1`, qr{xml_grep2 version \d+\.\d+$}, "version '$version' looks ok");
sub test_encoding
{ my( $command, $expected, $encoding, $message)= @_;
unlink $TMP if -f $TMP;
view release on metacpan or search on metacpan
By default it:
prints maximum 500 companies (API restriction)
looks for apikey and city in C<.ygeo> file. C<.ygeo> config has yaml syntax. Firsty it search C<.ygeo> file in current directory, then in home directory
=head1 AUTHOR
Pavel Serikov <pavelsr@cpan.org>
view release on metacpan or search on metacpan
bin/zipdetails view on Meta::CPAN
return (0, 0, '')
if $buffer ne "APK Sig Block 42" ;
# Step 2 - read the second length field
# and check that it looks ok
$buffer = readFromOffset($cdOffset - 16 - 8, 8);
my $len2 = unpack("Q<", $buffer);
return (0, 0, '')
if $len2 == 0 || $len2 > $FILELEN;
view release on metacpan or search on metacpan
lib/AppConfig/CGI.pm view on Meta::CPAN
my $state = AppConfig::State->new(\%cfg);
my $cgi = AppConfig::CGI->new($state);
$cgi->parse($cgi_query);
$cgi->parse(); # looks for CGI query in environment
=head1 OVERVIEW
AppConfig::CGI is a Perl5 module which implements a CGI interface to
AppConfig. It examines the QUERY_STRING environment variable, or a string
view release on metacpan or search on metacpan
lib/Appium/Android/CanPage.pm view on Meta::CPAN
# A node is interesting if it has a text, id, or content-desc
# attribute.
my $interesting_attrs = [ qw/text resource-id content-desc/ ];
foreach my $node (@nodes) {
# The inspect output for a single node looks like:
#
# $class_of_node
# text: $node_text
# resource-id: $node_id
# content-desc: $node_desc
view release on metacpan or search on metacpan
lib/Application/Config.pm view on Meta::CPAN
baz=bash
[My::Test::Class]
foo=baz
Would result in the config method returning a data structure that looks
something like:
{
'_' => {
'foo' => 'bar',
lib/Application/Config.pm view on Meta::CPAN
Calling pkgconfig from the My::Test::Class package would return only the
structure under the C<My::Test::Class> key.
=head1 WHERE ARE THE CONFIG FILES ON DISK?
Application config looks, in this order, for a config file:
=over 4
=item ~/.<filename>
view release on metacpan or search on metacpan
lib/Application/Pipeline.pm view on Meta::CPAN
=head2 The %plan
To build a pipeline application, it is necessary to register methods to run
during each phase. This can be done one at a time, with the C<addHandler>
method. But Application::Pipeline also looks in the subclass package for the
package variable C<%plan>. This hash's keys are the names of the phases of the
pipeline. Each key points to an array reference which is a list of the methods
to run for that phase. The methods are either the names of the methods to run,
or references to the actual methods.
view release on metacpan or search on metacpan
inc/Devel/PPPort.pm view on Meta::CPAN
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.010001||p
view release on metacpan or search on metacpan
share/files/public/skins/default/jquery-ui-1.9.1.custom/development-bundle/external/jshint.js view on Meta::CPAN
return t;
}
// Produce the next token. It looks for programming errors.
function advance(id, t) {
switch (token.id) {
case "(number)":
if (nexttoken.id === ".") {
share/files/public/skins/default/jquery-ui-1.9.1.custom/development-bundle/external/jshint.js view on Meta::CPAN
if (!nexttoken.labelled && nexttoken.value !== "{") {
warning("Label '{a}' on {b} statement.", nexttoken, t.value, nexttoken.value);
}
if (jx.test(t.value + ":")) {
warning("Label '{a}' looks like a javascript url.", t, t.value);
}
nexttoken.label = t.value;
t = nexttoken;
}
view release on metacpan or search on metacpan
t/03-document.t view on Meta::CPAN
$collection->create_document( { Hello => 'World' });
my $list = $collection->document_paths();
is ref($list) => "ARRAY" => "List of paths is an array";
like $list->[0] => qr!/_db/tmp_/_api/document/collection/\d+! => "path looks right";
$collection->create_document( q!{ "Hello" : "World" }! );
$list = $collection->document_paths();
is scalar(@$list), 2;
view release on metacpan or search on metacpan
t/03-document.t view on Meta::CPAN
is $count->{count}, 1;
my $list = $collection->document_paths();
is ref($list) => "ARRAY" => "List of paths is an array";
like $list->[0] => qr!/_db/tmp_/_api/document/collection/\d+! => "path looks right";
$collection->create_document( q!{ "Hello" : "World", "_key" : "baz" }! );
$list = $collection->document_paths();
is scalar(@$list), 2;
view release on metacpan or search on metacpan
lib/ArangoDB/BindVars.pm view on Meta::CPAN
package #Hiding package
ArangoDB::BindVars::Validator;
use strict;
use warnings;
use Scalar::Util qw(looks_like_number);
use Data::Util qw(:check);
use ArangoDB::ClientException;
sub validate {
my $val = shift;
view release on metacpan or search on metacpan
perllib/Arch/FileHighlighter.pm view on Meta::CPAN
/usr/bin/enscript is found.
It is possible to configure different filters ("none", "internal",
"enscript") depending on file name extension. In any case the resulting
markup is always unified, i.e. all special characters are HTML-encoded
using SGML entities, and the markup that looks like
E<lt>spanclass="syntax_foo"E<gt>barE<lt>/spanE<gt> is used.
=head1 METHODS
The following methods are available: