zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: SIGINT/TRAPINT Behaves Differently in 4.3.11
Date: Fri, 16 Sep 2011 10:17:42 -0700	[thread overview]
Message-ID: <CAH+w=7bF8Dex+ROnY1XDWTMvxSExVs8Pqzxo7mVvUDzs5jSCbA@mail.gmail.com> (raw)
In-Reply-To: <68D8247F-256A-4E0B-9DD5-B7B7C11B87D9@uga.edu>

On Thu, Sep 15, 2011 at 7:35 PM,  <sorin.ionescu@gmail.com> wrote:
>
> I have the following call tree: function prompt_theme_precmd() -> function git-info() -> SUBSHELL -> function git() ->  hub -> Git.
>
> On ZSH 4.3.10, pressing CTRL + C while the above is executing calls the shell's TRAPINT function, which is the expected behaviour, but since 4.3.11, SIGINT is sent only to the executing process (Git), and the shell's TRAPINT function is no longer called.
>
> However, pressing CTRL + C AFTER the prompt has been displayed calls TRAPINT.
>
> Is this a bug, or is this the new expected behaviour?

This may be related to zsh-workers/27169 and the related (extensive)
thread wherein on some platforms the shell was actually exiting on a
SIGINT received by a child process.  As you might be able to discern
from that thread, among other things it was never obvious whether some
of those changes should have been restricted to particular #ifdef
block.

Or it might not be related to that at all.

In any case the signal was likely never actually sent to the shell, it
was instead reacting to the exit status of whatever process did get
the signal.  Possibly the issue here is that now the intervening
subshell is not propagating interrupt via its exit status up to the
parent shell.


  reply	other threads:[~2011-09-16 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16  2:35 sorin.ionescu
2011-09-16 17:17 ` Bart Schaefer [this message]
2011-09-25 22:31   ` Bart Schaefer
2011-10-01 19:14     ` Peter Stephenson
2011-10-02 10:23       ` Julien Nicoulaud
2011-10-02 17:04         ` 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:
  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='CAH+w=7bF8Dex+ROnY1XDWTMvxSExVs8Pqzxo7mVvUDzs5jSCbA@mail.gmail.com' \
    --to=schaefer@brasslantern.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).