From: Vincent Lefevre <firstname.lastname@example.org>
Subject: Re: Ctrl-\ while executing a pipeline made zsh quit
Date: Tue, 26 Apr 2022 05:00:02 +0200 [thread overview]
Message-ID: <20220426030002.GC100943@zira.vinc17.org> (raw)
On 2022-04-25 18:24:15 -0700, Bart Schaefer wrote:
> On Mon, Apr 25, 2022 at 5:37 PM Vincent Lefevre <email@example.com> wrote:
> > With zsh 5.8.1 under Linux (zsh 5.8.1-1 Debian/unstable package),
> > while I was executing a pipeline, I typed Ctrl-\ to interrupt it
> > (Ctrl-C had no effect), which made unexpectedly zsh quit: SIGQUIT
> > should interrupt the commands zsh starts, not the interactive shell
> > itself.
> I'm unable to reproduce this on Ubuntu 20.04 with 184.108.40.206-test.
I can't reproduce it either. This may be a timing related issue:
perhaps there's some place where if a signal is received, everything
goes wrong (Ctrl-C normally has an effect, so perhaps things were
wrong when I first try Ctrl-C).
The only case I had found where Ctrl-C had no effect was this bug:
i.e. in case of process substitution, but here there was no such thing.
Or perhaps the cause of the issue was that here, the Ctrl-C didn't
kill the left-hand side (possibly because the ssh started by svn
got frozen... not sure).
> I vaguely recall there's actually a bug in some version(s?) of "less"
> that causes its parent to exit?
I'm not aware of that, and I don't see how this could be the fault
of "less" (unless it kills his parent, but why would it do this?).
> I did discover that if "less" exits with an error, the whole pipeline
> becomes unkillable with either INT or QUIT; the shell is hung until
> the left side exits.
If "less" really exits, how could this happen?
Vincent Lefèvre <firstname.lastname@example.org> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2022-04-26 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 0:36 Vincent Lefevre
2022-04-26 0:44 ` Vincent Lefevre
2022-04-26 1:24 ` Bart Schaefer
2022-04-26 3:00 ` Vincent Lefevre [this message]
2022-04-26 4:05 ` Bart Schaefer
2022-04-26 9:07 ` Vincent Lefevre
2022-04-26 9:18 ` pipeline that cannot be interrupted (was: Ctrl-\ while executing a pipeline made zsh quit) Vincent Lefevre
2022-04-26 10:07 ` pipeline that cannot be interrupted Vincent Lefevre
2022-04-27 20:07 ` Bart Schaefer
2022-04-27 20:29 ` Bart Schaefer
2022-04-29 0:24 ` 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).