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 an argument to your script.
BTW, JupiterHost didn't misunderstand you. He/she suspected what many of us did, that you were making the classic beginner's mistake of asking how to do one thing that may or may not be possible instead of looking at the big picture and coming at it from a 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 line that evoked script as string 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? <snip snootiness> -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
