On Wed, 25 Sep 2002, Nadav Har'El wrote:
> On Wed, Sep 25, 2002, Shlomi Fish wrote about "Re: Help with a Bourne Shell Script":
> > Sometimes I do "expr 5 \> 6 > /dev/null" instead.
>
> Well, you shouldn't... Expr wasn't meant for these ki
On Wed, Sep 25, 2002, Shlomi Fish wrote about "Re: Help with a Bourne Shell Script":
> Sometimes I do "expr 5 \> 6 > /dev/null" instead.
Well, you shouldn't... Expr wasn't meant for these kinds of things, and
you just saw how this can cause you bugs. Do &q
On Wed, 25 Sep 2002, Nadav Har'El wrote:
> On Wed, Sep 25, 2002, Shlomi Fish wrote about "Help with a Bourne Shell Script":
> > http://t2.technion.ac.il/~shlomif/fetchweb
> > My problem is that proc_args does not return the new command line.
>
> That'
On Wed, Sep 25, 2002, Shlomi Fish wrote about "Help with a Bourne Shell Script":
> http://t2.technion.ac.il/~shlomif/fetchweb
> My problem is that proc_args does not return the new command line.
That's because parse_args returned "0\n0\nyour arguments" instead of
On Wed, Sep 25, 2002 at 09:56:34AM +0300, Shlomi Fish wrote:
>
> Check:
>
> http://t2.technion.ac.il/~shlomif/fetchweb
>
> My problem is that proc_args does not return the new command line.
You probably meant 'test' and not expr in line 54.
expr, besides setting the return value, also outputs
Check:
http://t2.technion.ac.il/~shlomif/fetchweb
My problem is that proc_args does not return the new command line.
Regards,
Shlomi Fish
--
Shlomi Fish[EMAIL PROTECTED]
Home Page: http://t2.technio
