Re: CLOSED Re: Obtaining complete Unix command line that evoked script as string

2006-01-19 Thread Jeff Pang
rHost.Net" <[EMAIL PROTECTED]> >Sent: Jan 20, 2006 9:31 AM >To: Grant Jacobs <[EMAIL PROTECTED]>, beginners@perl.org >Subject: Re: CLOSED Re: Obtaining complete Unix command line that evoked >script as string > > > >Grant Jacobs wrote: >> >> Forced

Re: CLOSED Re: Obtaining complete Unix command line that evoked script as string

2006-01-19 Thread JupiterHost.Net
Grant Jacobs wrote: Forced to make time to get off this list as the volume is too much for the megre limit my ISP sets. Thanks again for those that helped; my working solution seems OK for now. Below is a reply to anonymous ("JupiterHost.Net"), anyone else is welcome to ignore it. Wri

CLOSED Re: Obtaining complete Unix command line that evoked script as string

2006-01-19 Thread Grant Jacobs
Forced to make time to get off this list as the volume is too much for the megre limit my ISP sets. Thanks again for those that helped; my working solution seems OK for now. Below is a reply to anonymous ("JupiterHost.Net"), anyone else is welcome to ignore it. Writing a new shell is qui

Re: CLOSED? Re: Obtaining complete Unix command line that evoked script as string

2006-01-15 Thread JupiterHost.Net
Like a lot of things, there isn't one "right" way to it, the final choice depends on the project, the budget, time constraints, etc. I'm Writing a new shell is quick and cheap? working with shell and perl; it may not be ideal, but is a given. Personally, its silly to tell me I'm an idiot wi

Re: CLOSED? Re: Obtaining complete Unix command line that evoked script as string

2006-01-14 Thread JupiterHost.Net
Hello, Originally my previous post had an explanation of why I really did want the pipes and redirects. I dropped it as I didn't want to be long-winded. Short version: large intermediate data files can be avoided by using pipes. Likewise, I frequently use multiple steps of filtering Ok, s

CLOSED? Re: Obtaining complete Unix command line that evoked script as string

2006-01-14 Thread Grant Jacobs
I'm going to trial a simplistic shell-based solution initially and later work on anything fancier (see at the end of the message). Thanks for the excursions and excuse my using the wrong forum. I'll just roll all my replies into one post and then stop taking over this forum :-) Im commin

Re: CLOSING Re: Obtaining complete Unix command line that evoked script as string

2006-01-13 Thread Jay Savage
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

RE: CLOSING Re: Obtaining complete Unix command line that evoked script as string

2006-01-13 Thread Bliss, Kevin
-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:

Re: Obtaining complete Unix command line that evoked script as string

2006-01-13 Thread Leif Ericksen
On Fri, 2006-01-13 at 11:02 +1300, Grant Jacobs wrote: > I'll be closing this unless I can see leads soon as I'm pretty much > out of time and I'll be unsubscribing when I'm done. That is fine do what you have to do... please read on... > As you can see, I really do "just need the command line"

Re: CLOSING Re: Obtaining complete Unix command line that evoked script as string

2006-01-13 Thread Jay Savage
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

Re: CLOSING Re: Obtaining complete Unix command line that evoked script as string

2006-01-13 Thread JupiterHost.Net
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

RE: CLOSING Re: Obtaining complete Unix command line that evoked script as string

2006-01-12 Thread Grant Jacobs
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

RE: CLOSING Re: Obtaining complete Unix command line that evoked script as string

2006-01-12 Thread Timothy Johnson
different angle. Sometimes what people ask for isn't what they need to meet their overall goal. -Original Message- From: Grant Jacobs [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 2:03 PM To: beginners@perl.org Subject: CLOSING Re: Obtaining complete Unix command l

CLOSING Re: Obtaining complete Unix command line that evoked script as string

2006-01-12 Thread Grant Jacobs
I'll be closing this unless I can see leads soon as I'm pretty much out of time and I'll be unsubscribing when I'm done. At 8:56 AM -0500 12/1/06, Bob Showalter wrote: I'm with JupiterHost; what exactly are you trying to accomplish here? I thought I'd already said that, but perhaps I missed

Re: *NOT* SOLVED Re: Obtaining complete Unix command line that evoked script as string

2006-01-12 Thread Leif Ericksen
Since most folks bottom post here see the bottom for my answer to this problem. On Thu, 2006-01-12 at 15:48 +1300, Grant Jacobs wrote: > Sorry for the repeat posting, that's NOT solved. > > >(Excuse the long post.) > > > >Unless I'm missing something, this doesn't do what I wanted. I want > >is

Re: SOLVED Re: Obtaining complete Unix command line that evoked script as string

2006-01-12 Thread Tom Phoenix
On 1/11/06, Grant Jacobs <[EMAIL PROTECTED]> wrote: > I want > is the whole command *line* > it'd be > nicer to have a solution that's not tied to a particular shell or > version.) Alas, only a few versions of a few shells will give you what you want. The command line which invoked your program,

Re: SOLVED Re: Obtaining complete Unix command line that evoked script as string

2006-01-12 Thread Bob Showalter
Grant Jacobs wrote: I want is the whole command *line*, not the portion of it that evoked the script, the latter being the individual *command* within the command line--confusing enough ;-) ? If I issue the example I gave in my OP: echo -n "Starting..." ; more some-stuff | \ doStuff.pl

Re: NOT SOLVED Re: Obtaining complete Unix command line that evoked script as string

2006-01-11 Thread JupiterHost.Net
echo -n "Starting..." ; more some-stuff | \ doStuff.pl - 3 > save-here.out ; echo "done." Within doStuff.pl I want to obtain the command line, i.e. everything from "echo" through to '"done."', or at least everything from "more" I think you may need to rethink your goal and try a differe

*NOT* SOLVED Re: Obtaining complete Unix command line that evoked script as string

2006-01-11 Thread Grant Jacobs
Sorry for the repeat posting, that's NOT solved. (Excuse the long post.) Unless I'm missing something, this doesn't do what I wanted. I want is the whole command *line*, not the portion of it that evoked the script, the latter being the individual *command* within the command line--confusi

SOLVED Re: Obtaining complete Unix command line that evoked script as string

2006-01-11 Thread Grant Jacobs
(Excuse the long post.) Unless I'm missing something, this doesn't do what I wanted. I want is the whole command *line*, not the portion of it that evoked the script, the latter being the individual *command* within the command line--confusing enough ;-) ? If I issue the example I gave in my

Re: Obtaining complete Unix command line that evoked script as string

2006-01-10 Thread JupiterHost.Net
Grant Jacobs wrote: Item: Obtaining complete Unix command line that evoked script as a string use Unix::PID; my $pid = Unix::PID->new(); print 'The kernel says I am: ' . $pid->get_command($$); -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <

Obtaining complete Unix command line that evoked script as string

2006-01-10 Thread Grant Jacobs
Item: Obtaining complete Unix command line that evoked script as a string If there is a more appropriate list for this, let me know; the other perl lists I've seen seem to specialised for this. I'm trying to get the complete command line that invoked a script as a string, that is the output o