From: Chet Ramey <chet.ramey@case.edu>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org, chet.ramey@case.edu
Subject: Re: set -e (no && or ||)
Date: Fri, 12 Oct 2012 09:49:32 -0400 [thread overview]
Message-ID: <50781FEC.3090309@case.edu> (raw)
In-Reply-To: <CAECNH1RQxAH3DvSCVagR_DQHqA6Cpi2U+0p9m3=rhp=kDSnGCQ@mail.gmail.com>
On 10/12/12 7:53 AM, Peter Stephenson wrote:
> On Fri, 12 Oct 2012 07:05:41 -0400
> Sergey Fadeev <hindsight@email.com> wrote:
>
>> Why doesn't it exit the shell?
>> $ set -e
>> $ echo $(false)
>> Shouldn't the error code of $(false) command substitution be checked
>> by set -e before passing stdout to the echo builtin?
>
> No, because the command was "echo", and that didn't fail. Exit status
> effectively means exit status seen by the main shell command
> interpreter ($?), although I'm sure there are some subtleties I haven't
> thought about.
>
> The way to get the status of a substitution to fail is to use an
> assignment:
>
> output=$(false)
>
> which does cause the shell to exit on failure, because it would set $? to
> 1. This is standard shell behaviour, though I can't point to where in
> the standard it says.
2.9.1 Simple Commands
If there is a command name, execution shall continue as described in
Command Search and Execution. If there is no command name, but the command
contained a command substitution, the command shall complete with the exit
status of the last command substitution performed. Otherwise, the command
shall complete with a zero exit status.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
prev parent reply other threads:[~2012-10-12 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 11:05 Sergey Fadeev
2012-10-12 11:53 ` Peter Stephenson
2012-10-12 13:29 ` Bart Schaefer
2012-10-12 13:49 ` Chet Ramey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50781FEC.3090309@case.edu \
--to=chet.ramey@case.edu \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).