help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Subject: Re: Ctrl-\ while executing a pipeline made zsh quit
Date: Tue, 26 Apr 2022 11:07:22 +0200	[thread overview]
Message-ID: <20220426090722.GD100943@zira.vinc17.org> (raw)
In-Reply-To: <CAH+w=7YXMTPgX-_pBqy_nE7vRg2bcGpu6gyBUA1r1jo4fQ3LNA@mail.gmail.com>

On 2022-04-25 21:05:11 -0700, Bart Schaefer wrote:
> On Mon, Apr 25, 2022 at 8:00 PM Vincent Lefevre <vincent@vinc17.net> wrote:
> >
> > > 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?
> When I couldn't replicate your problem, I thought perhaps I was
> running the mless function the wrong way, so I did this:
> ( zsh -fc 'print a few words; /bin/sleep 30' ) | mless -
> This causes less to exit with a no-such-file error, at which point all
> signals were ignored and no prompt returned until the "sleep 30"
> finished.

I wasn't using "mless" in that way, though this may be related to
what I got. Anyway, I think that this is a bug in zsh; this issue
is also reproducible with "head -n 1" instead of "less".

Vincent Lefèvre <vincent@vinc17.net> - 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)

  reply	other threads:[~2022-04-26  9:08 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
2022-04-26  4:05     ` Bart Schaefer
2022-04-26  9:07       ` Vincent Lefevre [this message]
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=20220426090722.GD100943@zira.vinc17.org \
    --to=vincent@vinc17.net \
    --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).