I have a script that asks a bunch of questions using the following method for input:
print "Name:";
while(<>){
chomp;
$name=$_;
}
So for example, if the questions asked for name, age, & color (in that order)... I want to be able to easily convert $ARGV into the input expected by... (2 Replies)
ok,
Newbie here.....
I just installed this solaris 10 for a class I'm taking. We couldn't figure out how to change the IP so we were told to just do it from the sys-uncofig process. Well, after I did that, I lost the GUI witch isn't all that bad cuz I want to learn the cli anyways, but I keep... (1 Reply)
Hello
I have simple script that will accept as arg string like this :
".../foo/blah/,.../.../foo1/,.../blah"
now perl automatically removes the slashes "/" , I can't escape the slashes in the input I have to control on it
so how can I force perl to not touch this slashes?
Thanks ... (5 Replies)
I have a project on which I have to use cpuinfo to get model name, number of cpus and bogomips.. for sys I need the uptime, total ram and from env I need the HOSTNAME.. from CMD ouputs i need the eth0-ip and .df..
The problem is that those modules have to be call from a subroutine and I have to... (0 Replies)
All of my machines (various open source derivatives on x86 and amd64) store argv above the stack (at a higher memory address). I am curious to learn if any systems store argv below the stack (at a lower memory address).
I am particularly interested in proprietary Unices, such as Solaris, HP-UX,... (9 Replies)
Hi ,
I need to match module data_tx_dig (
I tried matching
~m/module(\s+)ARGV(\s+)\(/ --> (generic code)but is not working.The same is able to match when i provide hardcoded value instead of passing from the command line.
~m/module(\s+)data_tx_dig(\s+)\(/ -->(hardcoded code).Please help me... (8 Replies)
Hello folks!
While "sedding" about again, I ran into this little conundrum du jour:#!/usr/bin/perl
use strict;
use warnings;
use diagnostics;
@ARGV = ('./afile.dat', './*.txt');
$^I = '';
while (<>)
{
s/Twinkies/Dinner/g;
print;
}When run, perl complains,...but, of... (1 Reply)
Hello folks!
While "sedding" about again, I ran into this little conundrum du jour:#!/usr/bin/perl
use strict;
use warnings;
use diagnostics;
@ARGV = ('./afile.dat', './*.txt');
$^I = '';
while (<>)
{
s/Twinkies/Dinner/g;
print;
}When run, perl complains,...but, of... (2 Replies)
(Apologies for any typos.)
OSX 10.12.3 AND Windows 10.
This is for the serious Python experts on at least 3.5.x and above...
In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly.
Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies
LEARN ABOUT OPENDARWIN
after
after(n) Tcl Built-In Commands after(n)
__________________________________________________________________________________________________________________________________________________NAME
after - Execute a command after a time delay
SYNOPSIS
after ms
after ms ?script script script ...?
after cancel id
after cancel script script script ...
after idle ?script script script ...?
after info ?id?
_________________________________________________________________DESCRIPTION
This command is used to delay execution of the program or to execute a command in background sometime in the future. It has several forms,
depending on the first argument to the command:
after ms
Ms must be an integer giving a time in milliseconds. The command sleeps for ms milliseconds and then returns. While the command is
sleeping the application does not respond to events.
after ms ?script script script ...?
In this form the command returns immediately, but it arranges for a Tcl command to be executed ms milliseconds later as an event
handler. The command will be executed exactly once, at the given time. The delayed command is formed by concatenating all the
script arguments in the same fashion as the concat command. The command will be executed at global level (outside the context of
any Tcl procedure). If an error occurs while executing the delayed command then the bgerror mechanism is used to report the error.
The after command returns an identifier that can be used to cancel the delayed command using after cancel.
after cancel id
Cancels the execution of a delayed command that was previously scheduled. Id indicates which command should be canceled; it must
have been the return value from a previous after command. If the command given by id has already been executed then the after can-
cel command has no effect.
after cancel script script ...
This command also cancels the execution of a delayed command. The script arguments are concatenated together with space separators
(just as in the concat command). If there is a pending command that matches the string, it is cancelled and will never be executed;
if no such command is currently pending then the after cancel command has no effect.
after idle script ?script script ...?
Concatenates the script arguments together with space separators (just as in the concat command), and arranges for the resulting
script to be evaluated later as an idle callback. The script will be run exactly once, the next time the event loop is entered and
there are no events to process. The command returns an identifier that can be used to cancel the delayed command using after can-
cel. If an error occurs while executing the script then the bgerror mechanism is used to report the error.
after info ?id?
This command returns information about existing event handlers. If no id argument is supplied, the command returns a list of the
identifiers for all existing event handlers created by the after command for this interpreter. If id is supplied, it specifies an
existing handler; id must have been the return value from some previous call to after and it must not have triggered yet or been
cancelled. In this case the command returns a list with two elements. The first element of the list is the script associated with
id, and the second element is either idle or timer to indicate what kind of event handler it is.
The after ms and after idle forms of the command assume that the application is event driven: the delayed commands will not be executed
unless the application enters the event loop. In applications that are not normally event-driven, such as tclsh, the event loop can be
entered with the vwait and update commands.
SEE ALSO
bgerror(n), concat(n), update(n), vwait(n)
KEYWORDS
cancel, delay, idle callback, sleep, time
Tcl 7.5 after(n)