Searched +refs:modify +refs:screen +refs:parameters (Results 1 - 15 of 15) sorted by relevance

/macosx-10.9.5/CPANInternal-140/Log-Dispatch/lib/Log/Dispatch/
H A DScreen.pm55 Log::Dispatch::Screen - Object for logging to the screen
61 my $screen = Log::Dispatch::Screen->new( name => 'screen',
65 $screen->log( level => 'alert', message => "I'm searching the city for sci-fi wasabi\n" );
69 This module provides an object for logging to the screen (really
78 This method takes a hash of parameters. The following options are
113 The callbacks are expected to modify the message and then return a
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/Log4perl/
H A DCatalyst.pm236 to the screen or to log files, but also to databases, email appenders,
277 If called without parameters, new() initializes Log4perl in a way
281 will call Log4perl with these parameters.
337 This library is free software; you can redistribute it and/or modify
H A DFAQ.pm27 the screen and a log file.
299 =head2 My application is already logging to a file. How can I duplicate all messages to also go to the screen?
312 the logfile and the screen. No reason to change your code, of course,
332 by defining a root logger with a screen appender, which would duplicate
333 messages from all your file loggers to the screen due to Log4perl's
409 it by one will cause it to log the calling function's parameters, not
583 But, you also want it to take command line parameters to set values
784 to the screen:
900 to the screen in a configurable color. Just create a new class
1354 parameters
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Dispatch-2.34/lib/Log/
H A DDispatch.pm306 name => 'screen',
322 logging objects to it (such as a file logger or screen logger). Then you
328 log file, via email, to the screen, and anywhere else, all with very
334 The constructor (C<new>) takes the following parameters:
351 See L<OUTPUT CLASSES> for the parameters that can be used when creating an
365 The callbacks are expected to modify the message and then return a
503 The following common parameters can be used when creating an output class.
504 All are optional. Most output classes will have additional parameters beyond
535 The callbacks are expected to modify the message and then return a
/macosx-10.9.5/CPANInternal-140/Log-Dispatch/lib/Log/
H A DDispatch.pm240 The callbacks are expected to modify the message and then return a
348 compatible. If I were to add more parameters to the C<log> call, it
351 parameters to the C<log> method will never be integrated into these
353 the parameters given to the C<log> method.
394 logger or screen logger). Then you call the C<log> method of the
400 log file, via email, to the screen, and anywhere else, all with very
505 program is free software; you can redistribute it and/or modify it
/macosx-10.9.5/CPANInternal-140/Perl-Tidy-20121207/bin/
H A Dperltidy8 # give Macs a chance to provide command line parameters
41 A convenient aid to systematically defining a set of style parameters
49 numerous input parameters, which are described in L<"FORMATTING
143 order of parameters is important, with later parameters overriding the
144 values of earlier parameters.
151 Most parameters which serve as on/off flags can be negated with a
166 The following parameters concern the files which are read and written.
229 =item B<-b>, B<--backup-and-modify-in-place>
290 any error message may mess up your screen, s
[all...]
/macosx-10.9.5/CPANInternal-140/Perl-Tidy/bin/
H A Dperltidy8 # give Macs a chance to provide command line parameters
40 A convenient aid to systematically defining a set of style parameters
48 numerous input parameters, which are described in L<"FORMATTING
138 order of parameters is important, with later parameters overriding the
139 values of earlier parameters.
146 Most parameters which serve as on/off flags can be negated with a
161 The following parameters concern the files which are read and written.
224 =item B<-b>, B<--backup-and-modify-in-place>
257 any error message may mess up your screen, s
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/
H A DLog4perl.pm264 sub easy_init { # Initialize the root logger with a screen appender
555 log messages to ("Print it to the screen and also append it to /tmp/my.log")
574 log file". And all this is possible by just changing the parameters
649 my($logger, $some, $other, $parameters) = @_;
805 to log to the screen, to files and to databases.
895 screen appender above, on the other hand,
913 advantage that you can modify your system's logging behaviour without
967 to C<Log::Log4perl::Appender::Screen>) to write to the screen. And
1107 If you're afraid that the way you're generating the parameters to the
1428 C<get_logger("")>, call it without parameters (
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/
H A DLog4perl.pm270 sub easy_init { # Initialize the root logger with a screen appender
699 log messages to ("Print it to the screen and also append it to /tmp/my.log")
718 log file". And all this is possible by just changing the parameters
793 my($logger, $some, $other, $parameters) = @_;
977 to log to the screen, to files and to databases.
1067 screen appender above, on the other hand,
1116 advantage that you can modify your system's logging behaviour without
1170 to C<Log::Log4perl::Appender::Screen>) to write to the screen. And
1314 If you're afraid that generating the parameters to the
1657 C<get_logger("")>, call it without parameters (
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/
H A DREADME74 log messages to ("Print it to the screen and also append it to
90 possible by just changing the parameters in a configuration file, which
160 my($logger, $some, $other, $parameters) = @_;
331 to log to the screen, to files and to databases.
418 The screen appender above, on the other hand, uses a "SimpleLayout",
464 unbeatable advantage that you can modify your system's logging behaviour
519 to "Log::Log4perl::Appender::Screen") to write to the screen. And "R", a
656 If you're afraid that generating the parameters to the logging function
972 "get_logger("")", call it without parameters ("get_logger()"), you'll
1083 will call the "preinit_callback" function without parameters
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/
H A DREADME74 log messages to ("Print it to the screen and also append it to
90 possible by just changing the parameters in a configuration file, which
160 my($logger, $some, $other, $parameters) = @_;
306 to log to the screen, to files and to databases.
393 The screen appender above, on the other hand, uses a "SimpleLayout",
408 unbeatable advantage that you can modify your system's logging behaviour
463 to "Log::Log4perl::Appender::Screen") to write to the screen. And "R", a
596 If you're afraid that the way you're generating the parameters to the of
889 "get_logger("")", call it without parameters ("get_logger()"), you'll
1275 defined priority and a screen appende
[all...]
/macosx-10.9.5/CPANInternal-140/Net-Telnet/lib/Net/
H A DTelnet.pm5 ## modify it under the same terms as Perl itself.
2295 $parameters,
2336 elsif ($nextchar eq "\372") { # start of subnegotiation parameters
2353 $parameters = substr $subcmd, 3, length($subcmd) - 5;
2356 $parameters = "";
2360 &$callback($self, $option, $parameters);
3494 Two different styles of named parameters are supported. This document
3519 entire terminal screen.
3531 optional parameters.
3565 corresponding named parameters
[all...]
/macosx-10.9.5/CPANInternal-140/Net-Telnet-3.03/lib/Net/
H A DTelnet.pm5 ## modify it under the same terms as Perl itself.
2295 $parameters,
2336 elsif ($nextchar eq "\372") { # start of subnegotiation parameters
2353 $parameters = substr $subcmd, 3, length($subcmd) - 5;
2356 $parameters = "";
2360 &$callback($self, $option, $parameters);
3494 Two different styles of named parameters are supported. This document
3519 entire terminal screen.
3531 optional parameters.
3565 corresponding named parameters
[all...]
/macosx-10.9.5/CPANInternal-140/Perl-Ldap/contrib/
H A Dtklkup5 # modify it under the terms of the GNU GENERAL PUBLIC LICENSE.
4884 #$mesg = $Global{ldap}->modify($entry);
5674 $mesg = $Global{ldap}->modify( $Global{'entryDN'}, add => $Global{'add'});
5699 $rmesg = $Global{rldap}->modify( $Global{'entryDN'}, add => $Global{'add'});
5777 $mesg = $Global{ldap}->modify( $Global{'entryDN'}, delete => $Global{'delete'});
5801 $rmesg = $Global{rldap}->modify( $Global{'entryDN'}, delete => $Global{'delete'});
5879 $mesg = $Global{ldap}->modify( $Global{'entryDN'}, replace => $Global{'replace'});
5903 $rmesg = $Global{rldap}->modify( $Global{'entryDN'}, replace => $Global{'replace'});
6311 During initial program initialization a "splash" screen will
6313 that the user will never see the splash screen i
[all...]
/macosx-10.9.5/vim-53/runtime/autoload/
H A Dnetrw.vim2467 " the variable below avoids that second refresh of the screen. The s:LocalBrowseShellCmdRefresh()
4016 " refresh screen and return to saved position
6460 " call Decho("modify display if wide/tree listing style")
7701 " restore top-of-screen line
7718 " netrw#NetrwSavePosn: saves position of cursor on screen {{{2
7727 " Save top-of-screen line
7731 " set up string holding position parameters

Completed in 319 milliseconds