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
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
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
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
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
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
