help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Ctrl-\ while executing a pipeline made zsh quit
Date: Mon, 25 Apr 2022 18:24:15 -0700	[thread overview]
Message-ID: <CAH+w=7Z2CG4wWgV31MLLtM64BCfu2Dt-N6oYzb8krY+wvCrqyw@mail.gmail.com> (raw)
In-Reply-To: <20220426003649.GA100943@zira.vinc17.org>

On Mon, Apr 25, 2022 at 5:37 PM Vincent Lefevre <vincent@vinc17.net> 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

I vaguely recall there's actually a bug in some version(s?) of "less"
that causes its parent to exit?

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.

  parent reply	other threads:[~2022-04-26  1:24 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 [this message]
2022-04-26  3:00   ` Vincent Lefevre
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7Z2CG4wWgV31MLLtM64BCfu2Dt-N6oYzb8krY+wvCrqyw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \


* 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).