On 1/13/06, Bliss, Kevin <[EMAIL PROTECTED]> wrote:
>
>
> -Original Message-
> From: Jay Savage [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 13, 2006 11:35 AM
> To: Grant Jacobs; beginners perl
> Subject: Re: CLOSING Re: Obtaining complete Unix command li
-Original Message-
From: Jay Savage [mailto:[EMAIL PROTECTED]
Sent: Friday, January 13, 2006 11:35 AM
To: Grant Jacobs; beginners perl
Subject: Re: CLOSING Re: Obtaining complete Unix command line that evoked
script as string
On 1/12/06, Grant Jacobs <[EMAIL PROTECTED]> wrote:
On 1/12/06, Grant Jacobs <[EMAIL PROTECTED]> wrote:
> >So sorry to see you go.
>
> There's nothing bad about me unsubscribing (you're reading me very
> negatively!). Its just I get so much mail that I prefer to
> unsubscribe and browse HTML archives if I'm not actively asking
> something.
>
>
> >Th
Lief, no, you're joining JupiterHost in misreading my posts (!): command
*line*, not *command*. It is a bit subtle, but its also the whole point
I'm not misunderstanding, you are :)
You want:
echo "foo" | script.pl -p 100 > foo.txt
not just:
script.pl -p 100
The point is:
How can a s
So sorry to see you go.
There's nothing bad about me unsubscribing (you're reading me very
negatively!). Its just I get so much mail that I prefer to
unsubscribe and browse HTML archives if I'm not actively asking
something.
The only cross-platform, foolproof way of keeping track of the
c
So sorry to see you go.
The only cross-platform, foolproof way of keeping track of the
command-line used to launch a program regardless of the complexity that
I can think of is to make a note of it in the program that launched the
command-line. If you really wanted to, you could even pass it as
