view release on metacpan or search on metacpan
root/base/terms/add view on Meta::CPAN
</tr>
</table>
<style type="text/css">
.yui-overlay { position:absolute;background:transparent;border:none;padding:none;margin:none; }
</style>
<!-- message preview majick -->
<script type="text/javascript">
(function () {
root/base/terms/add view on Meta::CPAN
var pWidth = obj.user_input.clientWidth,
pHeight = obj.user_input.clientHeight,
pLeft = obj.user_input.offsetLeft,
pTop = obj.user_input.offsetTop;
obj.preview_overlay = new YAHOO.widget.Overlay(
"preview_overlay",
{
context: [obj.config.user_input, 'tl', 'tl'],
visible: true,
width: obj.user_input.clientWidth + 'px',
height: obj.user_input.clientHeight + 'px'
}
);
obj.preview_overlay.setBody(data.formatted);
obj.preview_overlay.render(document.body);
Dom.get('preview_overlay').style.overflow = 'auto';
// update the button
obj.trigger.value = '[%l('Edit')%]';
root/base/terms/add view on Meta::CPAN
this.edit = function() {
// update the button
this.trigger.value = '[%l('Preview')%]';
this.user_input.style.visibility = 'visible';
this.preview_overlay.destroy();
YU.Event.removeListener( this.trigger, 'click' );
YU.Event.addListener(
this.trigger,
this.config.trigger_evt,
view release on metacpan or search on metacpan
lib/Path/Resolver.pm view on Meta::CPAN
#pod addressing content, they can easily be mixed and matched. Since resolvers know
#pod what kind of object they'll return, and can be fitted with translators, it's
#pod easy to ensure that all your multiplexed resolvers will resolve names to the
#pod same kind of object.
#pod
#pod For example, we could overlay two search paths like this:
#pod
#pod my $resolver = Path::Resolver::Resolver::Mux::Ordered->new({
#pod resolvers => [
#pod Path::Resolver::Resolver::FileSystem->new({ root => './config' }),
#pod Path::Resolver::Resolver::Archive::Tar->new({ archive => 'config.tgz' }),
lib/Path/Resolver.pm view on Meta::CPAN
addressing content, they can easily be mixed and matched. Since resolvers know
what kind of object they'll return, and can be fitted with translators, it's
easy to ensure that all your multiplexed resolvers will resolve names to the
same kind of object.
For example, we could overlay two search paths like this:
my $resolver = Path::Resolver::Resolver::Mux::Ordered->new({
resolvers => [
Path::Resolver::Resolver::FileSystem->new({ root => './config' }),
Path::Resolver::Resolver::Archive::Tar->new({ archive => 'config.tgz' }),
view release on metacpan or search on metacpan
lib/Paws/CodeBuild/ProjectEnvironment.pm view on Meta::CPAN
phase of your buildspec file:
If the operating system's base image is Ubuntu Linux:
C<- nohup /usr/local/bin/dockerd --host=unix:///var/run/docker.sock
--host=tcp://0.0.0.0:2375 --storage-driver=overlay&>
C<- timeout 15 sh -c "until docker info; do echo .; sleep 1; done">
If the operating system's base image is Alpine Linux and the previous
command does not work, add the C<-t> argument to C<timeout>:
C<- nohup /usr/local/bin/dockerd --host=unix:///var/run/docker.sock
--host=tcp://0.0.0.0:2375 --storage-driver=overlay&>
C<- timeout -t 15 sh -c "until docker info; do echo .; sleep 1; done">
=head2 RegistryCredential => L<Paws::CodeBuild::RegistryCredential>
view release on metacpan or search on metacpan
xt/grammars/Pg.pgx view on Meta::CPAN
func_expr_22: USER
func_expr_23: CURRENT_CATALOG
func_expr_24: CURRENT_SCHEMA
func_expr_25: CAST <LPAREN> a_expr AS Typename <RPAREN>
func_expr_26: EXTRACT <LPAREN> extract_list <RPAREN>
func_expr_27: OVERLAY <LPAREN> overlay_list <RPAREN>
func_expr_28: POSITION <LPAREN> position_list <RPAREN>
func_expr_29: SUBSTRING <LPAREN> substr_list <RPAREN>
func_expr_30: TREAT <LPAREN> a_expr AS Typename <RPAREN>
func_expr_31: TRIM <LPAREN> BOTH trim_list <RPAREN>
func_expr_32: TRIM <LPAREN> LEADING trim_list <RPAREN>
xt/grammars/Pg.pgx view on Meta::CPAN
extract_arg_7: SECOND
extract_arg_8: Sconst
# OVERLAY() arguments
# SQL99 defines the OVERLAY() function:
# o overlay(text placing text from int for int)
# o overlay(text placing text from int)
# and similarly for binary strings
overlay_list :
overlay_list_1
| overlay_list_2
overlay_list_1: a_expr overlay_placing substr_from substr_for
overlay_list_2: a_expr overlay_placing substr_from
overlay_placing: PLACING a_expr
# position_list uses b_expr not a_expr to avoid conflict with general IN
position_list: ( b_expr IN b_expr )?
# SUBSTRING() arguments
view release on metacpan or search on metacpan
share/perl-5.26/strtoull-fix-perl.h view on Meta::CPAN
/* According to strict ANSI C89 one cannot freely cast between
* data pointers and function (code) pointers. There are at least
* two ways around this. One (used below) is to do two casts,
* first the other pointer to an (unsigned) integer, and then
* the integer to the other pointer. The other way would be
* to use unions to "overlay" the pointers. For an example of
* the latter technique, see union dirpu in struct xpvio in sv.h.
* The only feasible use is probably temporarily storing
* function pointers in a data pointer (such as a void pointer). */
#define DPTR2FPTR(t,p) ((t)PTR2nat(p)) /* data pointer to function pointer */
view release on metacpan or search on metacpan
misc/IDE-support/server.pl view on Meta::CPAN
my $src = "";
while $_ = =<> {$src ~= $_;}
my $m = $src ~~ rx/oo/;
say "(mapcar 'delete-overlay (overlays-in (point-min) (point-max)))";
say "(overlay-put (make-overlay {$m.from +1} {$m.to +1} nil t t) 'face '(:foreground \"red\"))" if $m;
say '(message "did it")';
view release on metacpan or search on metacpan
what about a specialized filesystem to speedup dependency?
we "serialize" the dependency tree and let the filesystem do the triggering
this allows us to very fast know if a whole subtree has been modified or not
Problems to be fixed:
How do we serialize?
FUSE FAm nullfs overlayfs portalfs
each warp has a unique signature, we can keep a list of dependent in a warp signed file
each file in a dependency file get a 'special' file named: warp_sig + filename (ie X) in the
directory where the file is. The fs checks that file (and all other special file with
other warp sig for file X). The trace file (the special file) for a given warp signature
view release on metacpan or search on metacpan
share/static/jquery.magnific-popup.js view on Meta::CPAN
// Building markup
// main containers are created only once
if(!mfp.bgOverlay) {
// Dark overlay
mfp.bgOverlay = _getEl('bg').on('click'+EVENT_NS, function() {
mfp.close();
});
mfp.wrap = _getEl('wrap').attr('tabindex', -1).on('click'+EVENT_NS, function(e) {
view release on metacpan or search on metacpan
local/lib/perl5/Module/Build/Base.pm view on Meta::CPAN
}
return $ph->{features}->access($key, @_);
}
# No args - get the auto_features & overlay the regular features
my %features;
my %auto_features = $ph->{auto_features}->access();
while (my ($name, $info) = each %auto_features) {
my $failures = $self->prereq_failures($info);
my $disabled = grep( /^(?:\w+_)?(?:requires|conflicts)$/,
view release on metacpan or search on metacpan
bin/playwright_server view on Meta::CPAN
// var theFile = path.dirname(sharedir) + '/api.json';
// let rawdata = fs.readFileSync(theFile);
// This is automatically inserted via sed
let spec =
[{"name":"Accessibility","spec":[{"type":"text","text":"The Accessibility class provides methods for inspecting Chromium's accessibility tree. The accessibility tree is used by↵assistive technology such as [screen readers](https://en.wikipedia.org/...
function arr2hash (arr,primary_key) {
var inside_out = {};
for (var item of arr) {
inside_out[item.name] = item;
view release on metacpan or search on metacpan
t/data/book23 view on Meta::CPAN
great-hearted Odysseus within his house, and anointed him
with olive-oil, and cast about him a goodly mantle and a
doublet. Moreover Athene shed great beauty from his head
downwards, and made him greater and more mighty to behold,
and from his head caused deep curling locks to flow, like
the hyacinth flower. And as when some skilful man overlays
gold upon silver, one that Hephaestus and Pallas Athene
have taught all manner of craft, and full of grace is his
handiwork, even so did Athene shed grace about his head and
shoulders, and forth from the bath he came, in form like to
the immortals. Then he sat down again on the high seat,
view release on metacpan or search on metacpan
lib/Pod/Abstract/BuildNode.pm view on Meta::CPAN
return $begin;
}
=head2 for
my $for = node->for('overlay from <class>');
Create a =for node. The argument is the literal body of the for node,
no parsing will be performed.
=cut
view release on metacpan or search on metacpan
inc/inc_Module-Build/Module/Build/Base.pm view on Meta::CPAN
}
return $ph->{features}->access($key, @_);
}
# No args - get the auto_features & overlay the regular features
my %features;
my %auto_features = $ph->{auto_features}->access();
while (my ($name, $info) = each %auto_features) {
my $failures = $self->prereq_failures($info);
my $disabled = grep( /^(?:\w+_)?(?:requires|conflicts)$/,
view release on metacpan or search on metacpan
lib/PortageXS/Core.pm view on Meta::CPAN
#
# Parameters:
# $forcereload is optional and forces a reload of the make.conf and make.globals files.
#
# Example:
# @portdir_overlay=$pxs->getPortdirOverlay();
sub getPortdirOverlay {
my $self = shift;
my $forcereload = shift;
return split(/ /, $self->config->getParam('PORTDIR_OVERLAY', 'lastseen'));
view release on metacpan or search on metacpan
lib/Postscript/TextDecode.pm view on Meta::CPAN
'softhyphen' => chr(173),
'softsigncyrillic' => chr(1100),
'sohiragana' => chr(12381),
'sokatakana' => chr(12477),
'sokatakanahalfwidth' => chr(65407),
'soliduslongoverlaycmb' => chr(824),
'solidusshortoverlaycmb' => chr(823),
'sorusithai' => chr(3625),
'sosalathai' => chr(3624),
'sosothai' => chr(3595),
'sosuathai' => chr(3626),
'space' => chr(32),
lib/Postscript/TextDecode.pm view on Meta::CPAN
'ssangsioskorean' => chr(12614),
'ssangtikeutkorean' => chr(12600),
'ssuperior' => chr(63218),
'sterling' => chr(163),
'sterlingmonospace' => chr(65505),
'strokelongoverlaycmb' => chr(822),
'strokeshortoverlaycmb' => chr(821),
'subset' => chr(8834),
'subsetnotequal' => chr(8842),
'subsetorequal' => chr(8838),
'succeeds' => chr(8827),
'suchthat' => chr(8715),
lib/Postscript/TextDecode.pm view on Meta::CPAN
'tildebelowcmb' => chr(816),
'tildecmb' => chr(771),
'tildecomb' => chr(771),
'tildedoublecmb' => chr(864),
'tildeoperator' => chr(8764),
'tildeoverlaycmb' => chr(820),
'tildeverticalcmb' => chr(830),
'timescircle' => chr(8855),
'tipehahebrew' => chr(1430),
'tipehalefthebrew' => chr(1430),
'tippigurmukhi' => chr(2672),
view release on metacpan or search on metacpan
lib/Prima/OpenGL.pm view on Meta::CPAN
Selects either paletted or true-color visual representation.
=item layer INTEGER
x11: Layer zero corresponds to the main frame buffer of the display. Layer
one is the first overlay frame buffer, level two the second overlay frame
buffer, and so on. Negative buffer levels correspond to underlay frame
buffers.
win32: Provides only three layers, -1, 0, and 1 .
view release on metacpan or search on metacpan
Prima/PS/Unicode.pm view on Meta::CPAN
"\x{032F}" => 'breveinvertedbelowcmb',
"\x{0330}" => 'tildebelowcmb',
"\x{0331}" => 'macronbelowcmb',
"\x{0332}" => 'lowlinecmb',
"\x{0333}" => 'dbllowlinecmb',
"\x{0334}" => 'tildeoverlaycmb',
"\x{0335}" => 'strokeshortoverlaycmb',
"\x{0336}" => 'strokelongoverlaycmb',
"\x{0337}" => 'solidusshortoverlaycmb',
"\x{0338}" => 'soliduslongoverlaycmb',
"\x{0339}" => 'ringhalfrightbelowcmb',
"\x{033A}" => 'bridgeinvertedbelowcmb',
"\x{033B}" => 'squarebelowcmb',
"\x{033C}" => 'seagullbelowcmb',
"\x{033D}" => 'xabovecmb',
view release on metacpan or search on metacpan
lib/ProgressMonitor.pm view on Meta::CPAN
While 'ticking' is the primary way of informing the user, sometimes it makes sense
not only saying "I'm active", but also saying 'I'm currently doing this', i.e. a straightforward
message. Messages is a sort of out-of-band communication in regards to ticks. Depending
on how the monitor was set up, they may be ignored altogether, written using newlines 'beside'
the tick, or perhaps overlaying the tick field(s) (all or in part) - and then automatically
time out, restoring the tick fields. Anyway, feel free to give informational messages as
needed (but don't assume they'll be seen - just as with ticks, as the monitor in total
may be just a black hole).
=item FINISHING
view release on metacpan or search on metacpan
Prospect/Align.pm view on Meta::CPAN
# $Id: Align.pm,v 1.14 2003/11/07 00:46:09 cavs Exp $
# @@banner@@
=head1 NAME
Prospect::Align -- Package for overlaying multiple Prospect alignments
S<$Id: Align.pm,v 1.14 2003/11/07 00:46:09 cavs Exp $>
=head1 SYNOPSIS
view release on metacpan or search on metacpan
lib/Qgoda/Util.pm view on Meta::CPAN
return lc $str;
}
sub merge_data {
my ($data, $overlay) = @_;
# Return $overlay if it is of a different type than $data.
my $equal_ref = sub {
my ($x, $y) = @_;
return if !ref $x;
return if !ref $y;
lib/Qgoda/Util.pm view on Meta::CPAN
my $ref_y = reftype $y;
return $ref_x eq $ref_y;
};
return $overlay if !$equal_ref->($overlay, $data);
return $overlay if 'ARRAY' eq reftype $overlay;
my $merger;
$merger = sub {
my ($d, $o) = @_;
lib/Qgoda/Util.pm view on Meta::CPAN
$d->{$key} = $o->{$key};
}
}
};
$merger->($data, $overlay);
return $data;
}
sub interpolate($$) {
view release on metacpan or search on metacpan
Entanglement.pm view on Meta::CPAN
theory which are more easily understood. Hopefully this module will
shed some light on a few of these and their consequences.
One of the more popular interpretations of quantum mechanics holds that
instead of particles always being in a single, well defined, state
they instead exist as an almost ghostly overlay of many different
states (or values) at the same time. Of course, it is our experience
that when we look at something, we only ever find it in one single state.
This is explained by the many states of the particle collapsing to a
single state and highlights the importance of observation.
view release on metacpan or search on metacpan
lib/Quantum/Superpositions.pm view on Meta::CPAN
=head1 BACKGROUND
Under the standard interpretation of quantum mechanics, until they are observed, particles exist only as a discontinuous probability
function. Under the Cophenhagen Interpretation, this situation is often visualized by imagining the state of an unobserved particle to be
a ghostly overlay of all its possible observable
states simultaneously. For example, a particle
that might be observed in state A, B, or C may
be considered to be in a pseudo-state where
it is simultaneously in states A, B, and C.
Such a particle is said to be in a superposition of states.
view release on metacpan or search on metacpan
exercises/compile-tcsh/tcsh-6.10.00/nls/C/set2 view on Meta::CPAN
87 Priority changed
88 True deadlock detected
89 New input character
90 Stack limit exceeded
91 Unused signal
92 LM overlay
93 system freeze
94 system defreeze
95 dead lock
96 exceeded memory size limit
97 exceeded data size limit
view release on metacpan or search on metacpan
lib/RPM/Query.pm view on Meta::CPAN
our $VERSION = '0.03';
=head1 NAME
RPM::Query - Perl object overlay of the RPM query command
=head1 SYNOPSIS
use RPM::Query;
view release on metacpan or search on metacpan
lib/RPi/Serial.pm view on Meta::CPAN
operate correctly without this being done.
To disable Bluetooth on the Pi, edit the C</boot/config.txt>, and add the
following line:
dtoverlay=pi3-disable-bt-overlay
Save the file, then reboot the Pi.
=head1 METHODS
view release on metacpan or search on metacpan
t/25-raspi_config.t view on Meta::CPAN
like raspi_config, qr/core_freq/, "function includes data ok";
like
raspi_config,
qr/dtoverlay=pi3-disable-bt-overlay/,
"...and custom changes are included";
done_testing();
view release on metacpan or search on metacpan
lib/RPi/WiringPi.pm view on Meta::CPAN
serial bus.
See the linked documentation for full documentation on usage, or the
L<RPi::WiringPi::FAQ> for usage examples.
NOTE: Bluetooth on the Pi overlays the serial pins (14, 15) on the Pi. To use
serial, you must disable bluetooth in the C</boot/config.txt> file:
dtoverlay=pi3-disable-bt-overlay
=head2 servo($pin_num)
This method configures PWM clock and divisor to operate a typical 50Hz servo,
and returns a special L<RPi::Pin> object. These servos have a C<left> pulse of
view release on metacpan or search on metacpan
lib/RRDTool/OO.pm view on Meta::CPAN
optional => [qw(vertical_label title start end x_grid
y_grid alt_y_grid no_minor alt_y_mrtg
alt_autoscale alt_autoscale_max base
units_exponent units_length width
height interlaced imginfo imgformat
overlay unit lazy upper_limit lower_limit
rigid
logarithmic color no_legend only_graph
force_rules_legend title step draw
line area shift tick
print gprint vrule hrule comment font
lib/RRDTool/OO.pm view on Meta::CPAN
C<width>,
C<height>,
C<interlaced>,
C<imginfo>,
C<imgformat>,
C<overlay>,
C<unit>,
C<lazy>,
C<rigid>,
C<lower_limit>,
C<upper_limit>,
view release on metacpan or search on metacpan
inc/Module/Install/RTx/Factory.pm view on Meta::CPAN
^head1 SEE ALSO
This class allows \"overlay\" methods to be placed
into the following files _Overlay is for a System overlay by the original author,
_Vendor is for 3rd-party vendor add-ons, while _Local is for site-local customizations.
These overlay files can contain new subs or subs to replace existing subs in this module.
If you'll be working with perl 5.6.0 or greater, each of these files should begin with the line
no warnings qw(redefine);
so that perl does not kick and scream when you redefine a subroutine or variable in your overlay.
${class}_Overlay, ${class}_Vendor, ${class}_Local
^cut
view release on metacpan or search on metacpan
0.07_01 2008-11-06 Mike Peachey <zordrak@cpan.org>, Kevin Falcone <falcone@cpan.org>
- Complete code refactoring and updates for RT-3.8.x compatability.
0.06_03 2008-10-31 Mike Peachey <zordrak@cpan.org>, Kevin Falcone <falcone@cpan.org>
- Add fix to work around a plugin bug in RT-3.8.0 & RT-3.8.1 preventing
User_Vendor.pm overlay being required before RT::User is loaded.
- Check the return value from calling RT::User::Create.
- Check the return value when loading an autocreated user.
- README: Updated to talk about removing old files in local/.
- Added error-checking to complain if a an LDAP configuration is in use,
but no d_filter has been specified.