zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] Ctrl-C stops working after process substitution
Date: Tue, 10 Jul 2018 19:57:14 +0200	[thread overview]
Message-ID: <CAKc7PVAusDSoe0JiHm1hB6e0iZUTo-iZnd2fBFUya=A5jTrAAQ@mail.gmail.com> (raw)
In-Reply-To: <20180710152136eucas1p2a805a445f3687ad8a8eef97fe4bd2566~ACx3zdmM93266432664eucas1p2R@eucas1p2.samsung.com>

On 10 July 2018 at 17:21, Peter Stephenson <p.stephenson@samsung.com> wrote:
> On Tue, 10 Jul 2018 17:06:42 +0200
> Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
>> So what can mask SIGINT?
>
> This is usually a call to holdintr().

I tried setting breakpoint on holdintr and it wasn't called.

I had some realization that maybe child-process created by <() masks
SIGINT, and as it holds /dev/tty, this somehow leaks-out to the main
zsh-process, but this is naive theory, as currently I kill -9 the
child process instantly after reading needed data from it, so the
"leak" of SIGINT mask should at that moment be withdrawn. Who knows..


-- 
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin


  reply	other threads:[~2018-07-10 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04 11:47 Sebastian Gniazdowski
2018-07-04 12:09 ` Daniel Shahaf
2018-07-04 17:07   ` Sebastian Gniazdowski
2018-07-05  8:44     ` Peter Stephenson
2018-07-07 13:03       ` Sebastian Gniazdowski
2018-07-07 13:18         ` Sebastian Gniazdowski
2018-07-07 14:48       ` Sebastian Gniazdowski
2018-07-10 15:06         ` Sebastian Gniazdowski
2018-07-10 15:21           ` Peter Stephenson
2018-07-10 17:57             ` Sebastian Gniazdowski [this message]
2018-07-11  8:48               ` Sebastian Gniazdowski
2018-07-11 10:07                 ` Peter Stephenson

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='CAKc7PVAusDSoe0JiHm1hB6e0iZUTo-iZnd2fBFUya=A5jTrAAQ@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=p.stephenson@samsung.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).