zsh-workers
 help / color / mirror / code / Atom feed
From: Philippe Troin <phil@fifi.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Martin Cracauer <cracauer@cons.org>, zsh-workers@sunsite.dk
Subject: Re: zsh 4.3.10 terminates with SIGINT when one types Ctrl-G in emacs under Mac OS X
Date: 25 Jul 2009 23:24:35 -0700	[thread overview]
Message-ID: <8763dgkllo.fsf@old-tantale.fifi.org> (raw)
In-Reply-To: <090725115811.ZM23957@torch.brasslantern.com>

I've missed the beginning of the discussion, so excuse me if I restate
some points...

Bart Schaefer <schaefer@brasslantern.com> writes:

> Did you also see Eric Blake's assertion that the shell must not un-ignore
> a signal if it "starts life" with the signal ignored?  That's a "trap"
> command restriction I'd never discovered before (and one I'm not very
> happy about).

I would agree with that for non-interactive shells (that is zsh
interpreting a script).  However not resetting at least the terminal
signals (INT, QUIT, TTIN, TTOU, TSTP, CONT, HUP) to their default
settings (SIG_IGN) for interactive sessions could expose you to a lot
of trouble.  

> } On first sight it looks like the Linux kernel changes semantics based
> } on whether the terminal is in cooked mode or not.  Possibly in an
> } attempt to help a bit with the "what to do on SIGINT in interactive
> } programs" mess we are dealing with here.
> 
> I suspect it's more subtle than that ... e.g., it may be that on linux,
> the SIGINT isn't coming from the terminal driver at all.

Please enligthen me on this one...

Phil.


  reply	other threads:[~2009-07-26  6:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 18:18 Martin Cracauer
2009-07-25 18:58 ` Bart Schaefer
2009-07-26  6:24   ` Philippe Troin [this message]
2009-07-26 21:14     ` Bart Schaefer
2009-07-27 23:10   ` Martin Cracauer
2009-07-28  4:29     ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2009-07-12 20:59 Vincent Lefevre
2009-07-12 21:50 ` Bart Schaefer
2009-07-13  0:43   ` Vincent Lefevre
2009-07-13  2:36     ` Bart Schaefer
2009-07-13 18:39       ` Peter Stephenson
2009-07-16 16:24         ` Vincent Lefevre
2009-07-18  5:29           ` Bart Schaefer
2009-07-18 10:16             ` Vincent Lefevre
2009-07-18 18:16               ` Bart Schaefer
2009-07-19 18:03                 ` Bart Schaefer
2009-07-19 19:15                   ` Bart Schaefer
2009-07-19 20:14                     ` Bart Schaefer
2009-07-19 20:41                       ` Peter Stephenson
2009-07-18 18:35               ` Bart Schaefer
2009-07-18 23:09                 ` Vincent Lefevre
2009-07-19  9:51                   ` Vincent Lefevre
2009-07-19 16:32                     ` Bart Schaefer
2009-07-19 22:24                       ` Vincent Lefevre
2009-07-19 18:31                   ` Bart Schaefer
2009-07-20  8:31                     ` Vincent Lefevre
2009-07-22  2:58                       ` Eric Blake
2009-07-22  8:16                         ` Vincent Lefevre

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=8763dgkllo.fsf@old-tantale.fifi.org \
    --to=phil@fifi.org \
    --cc=cracauer@cons.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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).