bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange change between bash-3.2 and bash-4.0


From: Chet Ramey
Subject: Re: Strange change between bash-3.2 and bash-4.0
Date: Tue, 10 Feb 2009 17:35:29 -0500

> -e
>     When this option is on, if a simple command fails for any of the reasons
> listed in Consequences of Shell Errors or returns an exit status value >0, and
> is not part of the compound list following a while, until, or if keyword, and
> is not a part of an AND or OR list, and is not a pipeline preceded by the !
> reserved word, then the shell shall immediately exit.
> 
> 
> They are
> talking about simple commands, but later the words `is not a pipeline preceded
> by the ! reserved word' makes no sense, if they are talking only about simple
> commands...

That wording ("is not a pipeline") is intended to keep things like `! false'
from exiting the shell.  A simple command is a "degenerate" pipeline, and
the `!' reserved word applies only to pipelines.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    address@hidden    http://tiswww.tis.case.edu/~chet/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]