From: dana <dana@dana.is>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [BUG] err_exit misbehaviour involving function call inside else
Date: Fri, 15 Dec 2017 01:51:37 -0600 [thread overview]
Message-ID: <ADCCA733-C912-4F45-854E-510DEC19B3C5@dana.is> (raw)
In-Reply-To: <CAH+w=7aTcYQfwa_hqpW3qAcr88WNEt5TjyrxhovPxrSCz-VFXA@mail.gmail.com>
On 14 Dec 2017, at 17:00, Bart Schaefer <schaefer@brasslantern.com> wrote:
>In particular workers/41608 and workers/41615 ... I wonder if you have
>found the regression that wasn't found at the time of that patch.
>
>At the very least this sounds related.
It does certainly seem to be in the same general area.
It gives the '1' result in zsh 5.1.1, so it probably was not introduced by that
particular change. zsh 5.0.2 correctly produces '0', however. Maybe a clue.
dana
prev parent reply other threads:[~2017-12-15 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 22:40 dana
2017-12-14 23:00 ` Bart Schaefer
2017-12-15 7:51 ` dana [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=ADCCA733-C912-4F45-854E-510DEC19B3C5@dana.is \
--to=dana@dana.is \
--cc=schaefer@brasslantern.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).