From: Stephane Chazelas <stephane@chazelas.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [bug] errexit and cmdsubst after "else"
Date: Sat, 1 Feb 2020 17:56:36 +0000 [thread overview]
Message-ID: <20200201175636.u4drsthh574p5cia@chazelas.org> (raw)
From
https://unix.stackexchange.com/questions/565158/command-substitution-does-not-respect-err-exit-sometimes
$ zsh -ec 'if false; then;else a=$(false); echo $?; fi'
1
expected no output because of errexit.
That seems to be regression. @Gilles there bisected it to
https://sourceforge.net/p/zsh/code/ci/b581c3fece76c87ed86ae9fc704d0fcf208a79d3/
Which seemed to be a fix for a similar bug or regression:
http://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=36766
https://www.zsh.org/mla/workers/2015/msg02685.html
Possibly incomplete.
--
Stephane
next reply other threads:[~2020-02-01 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 17:56 Stephane Chazelas [this message]
2020-02-01 19:28 ` Peter Stephenson
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=20200201175636.u4drsthh574p5cia@chazelas.org \
--to=stephane@chazelas.org \
--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).