On Friday 27 January 2006 09:43 pm, Robert Persson wrote:
> On Thursday 26 January 2006 16:22 Richard Fish was like:
> > test doesn't output anything...it indicates success/failure with the
> > exit code.
>
> ...
>
> > As others have said though, watch out for the 'test' command built-in
> > to m
On Thursday 26 January 2006 16:22 Richard Fish was like:
> test doesn't output anything...it indicates success/failure with the
> exit code.
...
> As others have said though, watch out for the 'test' command built-in
> to many shells, as the behavior there is defined by the shell.
> Generally tho
On 1/26/06, Robert Persson <[EMAIL PROTECTED]> wrote:
> Someone was kind enough to send me a script that calls /usr/bin/test. When the
> script didn't work I realised that test was behaving strangely. Basically it
> doesn't seem to return anything.
test doesn't output anything...it indicates succe
On Thursday 26 January 2006 03:35 pm, Robert Persson wrote:
> Someone was kind enough to send me a script that calls /usr/bin/test. When
the
> script didn't work I realised that test was behaving strangely. Basically it
> doesn't seem to return anything.
>
> For instance "test -f /usr/bin/test"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Persson wrote:
> Someone was kind enough to send me a script that calls /usr/bin/test. When
> the
> script didn't work I realised that test was behaving strangely. Basically it
> doesn't seem to return anything.
>
> For instance "test -f /us
Someone was kind enough to send me a script that calls /usr/bin/test. When the
script didn't work I realised that test was behaving strangely. Basically it
doesn't seem to return anything.
For instance "test -f /usr/bin/test" doesn't display any output.
Nor does "test --help".
Nor "test --vers
6 matches
Mail list logo
