bug-bash
[Top][All Lists]
Advanced

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

Re: set -ue vs. (),{}


From: Paul Jarc
Subject: Re: set -ue vs. (),{}
Date: Mon, 11 Aug 2003 12:35:10 -0400
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)

Al Elgert <elgert@rbg.informatik.tu-darmstadt.de> wrote:
> Andy Goth schrieb am 07.08.2003 um 17:30:56 (-0500):
>> This is POSIX behavior, correct?  I haven't a clue where to check
>> the relevant standards documents... could you give me a pointer?
>
> I do not know if this is POSIX behaviour.

It is.
<URL:http://www.opengroup.org/onlinepubs/007904975/utilities/set.html>:
# -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.

<URL:http://www.opengroup.org/onlinepubs/007904975/utilities/xcu_chap02.html#tag_02_09_01>:
# Simple Commands
#
# A "simple command" is a sequence of optional variable assignments and
# redirections, in any sequence, optionally followed by words and
# redirections, terminated by a control operator.

"Simple commands" are distinct from "compound commands", described
later, which include () and {} lists.


paul




reply via email to

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