4 ms·
The nice way to write that isn't any kind of test command but: while true; do ...; done There is never any reason to use test, other than portability to so
by kazinator 3y ago
The nice way to write that isn't any kind of test command but:
while true; do ...; done
There is never any reason to use test, other than portability to some broken environment that is missing [ but not missing test.
- tuyiown 3y ago> There is never any reason to use test What's the reason for always using [ ?
- Diti 3y ago> There is never any reason to use test test -d /nix && echo "$_ exists" || echo "$_ doesn’t exist" You cannot do this with [ – Don’t Repeat Yourself, and your scripts become more maintainable. (Not POSIX-compliant. Documented in Bash and Zsh.)
- teo_zero 3y ago> You cannot do this with [ Why not? [ -d /nix ] && echo ...
- forgotpwd16 3y agoAs '$_' is set to last arg of previous run command, the test example will have it be the name of directory whereas for [ will always be ].
- elteto 3y agoD=/nix test -d $D && echo $D exists …
- cagey 3y ago$ V=nada echo "x${V}x" xx
- Dylan16807 3y agoV=nada; echo "x${V}x"
- teo_zero 3y agoAh yes, now I see it.
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- kazinator 3y agoIt's not working for me in a non-interactive Bash script on Bash 4.4. $_ is nto documented in the man page but is in the Info manual. It is not only set to the last argument of a command but also to the script name on script startup. $ bash --version GNU bash, version 4.4.20(1)-release (i686-pc-linux-gnu) [ ... ] Contents of script: $ cat underscore.sh #!/bin/sh # ^^ mistake here, should be /bin/bash test -e foo && echo $_ exists echo 'value of $_' = $_ Test: $ touch foo $ ./underscore.sh ./underscore.sh exists value of $_ = ./underscore.sh I'm seeing nothing but the behavior of $_ being set to the script, and not affected. But at the interactive prompt: $ test -e foo && echo $_ exists foo exists This doesn't look like something I can rely on in scripts. In the first place, I code in POSIX, except in the rare situation of making something that is strictly geared toward Bash. Magic global variables subject to hidden side effects are garbage; I already feel dirty enough when I have to use $?. This piece of crap also breaks under the DEBUG trap: $ debug() { > : > } $ trap debug DEBUG $ test -e foo && echo $_ exists debug exists $ test -e bar && echo $_ exists !1! (That !1! is how non-zero exit status is printed in my setup.) Sorry, I'm not going back to a 1978 way of writing shell tests, in order to use some broken magic variable.
- Diti 3y agoWow, I wasn’t aware of all these shortcomings! I will stop using it in my scripts too.
- watersb 3y agowhile true; do ...; done Is `true` a builtin? I might want to avoid an external process call just to create an unconditional loop.
- kazinator 3y agoPOSIX allows any command to be a builtin, as long as a real external command is also available which can be executed via execv and whatnot. $ echo $BASH_VERSION 4.4.20(1)-release $ type true true is a shell builtin Also: $ type test test is a shell builtin $ type [ [ is a shell builtin