From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: A serious bug in execution – where to debug?
Date: Tue, 30 Jul 2019 23:38:26 +0200 [thread overview]
Message-ID: <CAKc7PVC6vxkHRvRSQzPGxgOXLOMc-LyJaqA5DmsLXQ5tU8y3Hw@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMqkjK5hPxhhXYwp=4Sj49VfyZgEH06tK0vggnHyddbrsA@mail.gmail.com>
On Tue, 30 Jul 2019 at 23:02, Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>> On Tue, 30 Jul 2019 at 20:28, Bart Schaefer <schaefer@brasslantern.com> wrote:
>> > If you change the [[ ... ]] && ... to an if/then, does the behavior change?
>> > If you add a "return" or "return $?" at the end of the function, does it change?
>>
>> a) yes, the problem cancels with if-then
>> b) no, adding one of the return's doesn't change the behavior
>
> I think Bart solved it. Do you have `emulate -L zsh` in your `zle` function?
No, but adding it helps. Any emulation (sh, ksh) does. Aah, so this is
the errreturn option set within your plugin! and the if-then was
setting the return code to 0. A very interesting situation, having
your code called in foreign context, to know what options to defend
from.
next prev parent reply other threads:[~2019-07-30 21:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 17:00 Sebastian Gniazdowski
2019-07-30 17:05 ` Sebastian Gniazdowski
2019-07-30 17:41 ` Roman Perepelitsa
2019-07-30 17:55 ` Sebastian Gniazdowski
2019-07-30 18:12 ` Roman Perepelitsa
2019-07-30 18:16 ` Sebastian Gniazdowski
2019-07-30 18:22 ` Roman Perepelitsa
2019-07-30 18:53 ` Sebastian Gniazdowski
2019-07-30 19:23 ` Roman Perepelitsa
2019-07-30 19:34 ` Sebastian Gniazdowski
2019-07-30 19:41 ` Roman Perepelitsa
2019-07-30 19:59 ` Sebastian Gniazdowski
2019-07-30 20:08 ` Roman Perepelitsa
2019-07-30 20:38 ` Sebastian Gniazdowski
2019-07-30 18:27 ` Bart Schaefer
2019-07-30 18:46 ` Sebastian Gniazdowski
2019-07-30 21:02 ` Roman Perepelitsa
2019-07-30 21:38 ` Sebastian Gniazdowski [this message]
2019-07-30 21:45 ` Roman Perepelitsa
2019-07-30 21:54 ` Sebastian Gniazdowski
2019-07-30 22:11 ` Roman Perepelitsa
2019-07-30 22:18 ` Daniel Shahaf
2019-07-30 22:32 ` Roman Perepelitsa
2019-07-31 1:30 ` Sebastian Gniazdowski
2019-07-31 7:23 ` Roman Perepelitsa
2019-07-31 11:41 ` Sebastian Gniazdowski
2019-07-31 12:40 ` Roman Perepelitsa
2019-07-31 13:10 ` Sebastian Gniazdowski
2019-07-31 13:34 ` Roman Perepelitsa
2019-07-31 13:40 ` Sebastian Gniazdowski
2019-07-31 14:11 ` Roman Perepelitsa
2019-07-31 17:56 ` Sebastian Gniazdowski
2019-07-31 1:42 ` Bart Schaefer
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=CAKc7PVC6vxkHRvRSQzPGxgOXLOMc-LyJaqA5DmsLXQ5tU8y3Hw@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=roman.perepelitsa@gmail.com \
--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).