From: Peter Stephenson <email@example.com>
To: "Bart Schaefer" <firstname.lastname@example.org>,
"Jörg Sommer" <email@example.com>
Cc: Zsh Users <firstname.lastname@example.org>
Subject: Re: Zsh spins in endless loop with SIGHUP + read in zshexit
Date: Thu, 13 May 2021 17:07:10 +0100 (BST) [thread overview]
Message-ID: <email@example.com> (raw)
> On 13 May 2021 at 16:54 Bart Schaefer <firstname.lastname@example.org> wrote:
> On Thu, May 13, 2021 at 3:18 AM Jörg Sommer <email@example.com> wrote:
> > I'm using `read` in `zshexit` and when my terminal crashes (e.g. XTerm gets
> > killed or ssh connection dies) Zsh spins in an endless loop until I kill it
> > with SIGKILL (SIGTERM doesn't work).
> > [...]
> > So, if `raw_getbyte` returns `0` `zexit` gets called again. I think this
> > causes the loop.
> Yep. zexit() is a no-op there because it doesn't allow itself to
> execute recursively.
> There might be other places where similar loops can be triggered. I
> see just now PWS has also produced a different patch, which requires
> that zexit() return a value; I have no opinion on whether that's
> actually preferable.
I think the only possible issue with just a break would be if we didn't
want to return immediately. But I don't think that's an issue here:
zexit() can't do it's "ooh! you've got jobs" because it's way too late,
and the repeat over multiple ^D's is handled down here in ZLE anyway,
so it's in a position to know that's no-go as well. So don't see why
your simple patch shouldn't work.
next prev parent reply other threads:[~2021-05-13 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 10:17 Jörg Sommer
2021-05-13 14:36 ` Daniel Shahaf
2021-07-18 19:11 ` Lawrence Velázquez
2021-07-27 3:14 ` Daniel Shahaf
2021-05-13 15:51 ` Peter Stephenson
2021-05-13 15:54 ` Bart Schaefer
2021-05-13 16:07 ` Peter Stephenson [this message]
2021-05-13 16:30 ` Bart Schaefer
2021-05-13 18:44 ` Peter Stephenson
2021-05-13 21:37 ` Bart Schaefer
2021-05-14 9:56 ` Peter Stephenson
2021-05-14 17:44 ` Peter Stephenson
2021-05-14 18:51 ` Bart Schaefer
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).