karound for a similar (same?) problem in the archive:
http://groups.google.com/group/gnu.bash.bug/browse_thread/thread/5f84f1f50b4715ae/0d8283b2c2025dc0?lnk=gst&q=errexit#0d8283b2c2025dc0
However isn't this inconsistency a bug? I also tried this in dash and zsh, and
they both exit c
On Mon, Oct 06, 2008 at 09:22:30AM -0400, Chet Ramey wrote:
> Marcin Owsiany wrote:
>
> > I expected that if a simple pipeline failure causes the shell to exit, and
> > a simple for loop failure causes it to exit, then a failure in their
> > combination would also caus
you would also have to
fix cases such as:
set -e
true && false
echo done
As they are not simple commands either, right? The manpage even
explicitly says that it "does not exit if the command that fails is
[...] part of a && or ││ list".
Marcin
--
Marcin Owsiany <[EMAI
