Re: set -e, braces and compound commands

On 2/10/11 11:08 PM, Daniel Villeneuve wrote: > I'm using GNU bash, version 4.1.2(1)-release (i386-redhat-linux-gnu). > > Following the change of semantics of "set -e" in bash 4,"man bash" seems to > imply that the following script should exit after the for command (from the > text "or one of the

Re: set -e, braces and compound commands

Daniel Villeneuve writes: > For reference, I've consulted > http://thread.gmane.org/gmane.comp.standards.posix.austin.general/282, > http://thread.gmane.org/gmane.comp.shells.bash.bugs/13465 and > the current public POSIX spec I have access to which still says: > > *-e* >When this option is o

set -e, braces and compound commands

I'm using GNU bash, version 4.1.2(1)-release (i386-redhat-linux-gnu). Following the change of semantics of "set -e" in bash 4,"man bash" seems to imply that the following script should exit after the for command (from the text "or one of the commands executed as part of a command list enclosed