Re: [[ and set -E vs trap ERR

Isaac Good wrote: Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc'

[[ and set -E vs trap ERR

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -

Re: set -e vs. !

Dan Jacobson [EMAIL PROTECTED] writes: $ cat t.sh set -ex ! true #should stop here but doesn't!?! RTFM. `-e' Exit immediately if ..., unless ... the command's return status is being inverted using `!'. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE

Re: set -e vs. !

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dan Jacobson on 9/8/2006 5:42 AM: $ cat t.sh set -ex ! true #should stop here but doesn't!?! ! false true false : already quit $ bash t.sh + true + false + true + false $ pdksh t.sh + true Bash is right. This is a bug in