From: Bart Schaefer <schaefer@brasslantern.com>
To: mvxxc@gmx.de, zsh-workers@zsh.org
Subject: Re: Bug report
Date: Fri, 26 Dec 2014 18:35:16 -0800 [thread overview]
Message-ID: <141226183516.ZM18384@torch.brasslantern.com> (raw)
In-Reply-To: <20141226165344.GC1003@basilisk>
On Dec 26, 5:53pm, mvxxc@gmx.de wrote:
} Subject: Bug report
}
} If the following script is run in an empty directory, zsh executes the
} defined function only once.
Changing this line:
} set -e
To "set -exv" shows that func is in fact called twice but exits without
doing anything on the second call.
I therefore suspect one of workers/32568 or workers/32569.
This is very tricky because we have to propagate the value of $? from
before the "for" keyword (including before the start of the function)
into the "do" body, but must *not* *use* the value of $? for deciding
whether to exit-on-error, because the nonzero value came from an "if"
test. There is a "noerrexit" flag that is supposed to cover this case,
but it's not set when the very first "sublist" in a function body is
a for-loop (there are likely to be other similar cases).
next prev parent reply other threads:[~2014-12-27 2:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 16:53 mvxxc
2014-12-27 2:35 ` Bart Schaefer [this message]
2014-12-28 0:32 ` [PATCH] ERR_EXIT with "for" loops and shell functions (Re: Bug report) Bart Schaefer
2015-01-02 16:56 ` Peter Stephenson
2015-01-02 18:56 ` Bart Schaefer
2015-01-02 20:15 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2021-03-01 9:43 BUG REPORT ZheNing Hu
2021-03-01 15:27 ` Daniel Shahaf
2021-03-01 17:32 ` Bart Schaefer
2021-03-05 7:51 ` ZheNing Hu
2019-09-19 11:16 Bug report Vladimir Deyter
2019-09-19 14:53 ` Mikael Magnusson
2019-09-19 15:57 ` Daniel Shahaf
2014-09-17 0:26 bug report Mica Chimera
2014-09-17 1:08 ` Frank Terbeck
2014-06-05 17:05 robin terrep-drangiug
2014-06-05 20:48 ` Bart Schaefer
2013-12-17 10:59 Bug report Patrick Oscity
2013-12-17 11:27 ` Peter Stephenson
2013-12-17 17:11 ` Bart Schaefer
2013-12-17 17:56 ` Bart Schaefer
2013-12-14 18:44 Patrick Oscity
2013-12-14 19:08 ` Bart Schaefer
2013-12-14 20:43 ` Peter Stephenson
2013-12-15 1:15 ` Bart Schaefer
2013-12-15 13:30 ` Peter Stephenson
2013-12-15 17:10 ` Bart Schaefer
2013-12-15 1:08 ` Patrick Oscity
2013-12-15 11:01 ` Patrick Oscity
2013-08-04 12:16 Bug Report Yuusuke Yoshimoto
2013-08-04 17:58 ` Peter Stephenson
1996-05-22 0:07 Bug report Felix von Leitner
1996-05-15 7:48 Martin Birgmeier
1996-05-10 8:30 Martin Birgmeier
1995-08-24 11:23 Bug Report Carsten Friedrich
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=141226183516.ZM18384@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=mvxxc@gmx.de \
--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).