zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zefram <zefram@dcs.warwick.ac.uk>
Cc: zsh-workers@math.gatech.edu
Subject: Re: signal weirdness
Date: Wed, 13 Nov 1996 10:32:08 -0800	[thread overview]
Message-ID: <961113103209.ZM29344@candle.brasslantern.com> (raw)
In-Reply-To: Zefram <zefram@dcs.warwick.ac.uk> "Re: signal weirdness" (Nov 13,  6:03pm)

On Nov 13,  6:03pm, Zefram wrote:
} Subject: Re: signal weirdness
}
} I don't see the problem with just ignoring the situation, in the case
} of key-generated interrupts.  If the user wants to kill a program *and*
} have the shell process a SIGINT handler, he can press ^C twice.  HUP is
} the only one that we really need to handle specially.

Csh, at least, invokes its onintr handlers when any process spawned from
a csh script gets a keyboard interrupt.  /bin/sh (pre-POSIX, at least)
invokes its INT traps on a single interrupt, AFAIK.

Sometimes the shell is in a loop spawning jobs too fast for pressing ctrl-C
twice to have the desired effect.  What good is an INT handler if zsh never
gets the signal?

} What does POSIX say about all of this?

I'd be interested, too.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern


      reply	other threads:[~1996-11-13 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-13 14:06 Zefram
1996-11-13 17:41 ` Bart Schaefer
1996-11-13 18:03   ` Zefram
1996-11-13 18:32     ` Bart Schaefer [this message]

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=961113103209.ZM29344@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=schaefer@nbn.com \
    --cc=zefram@dcs.warwick.ac.uk \
    --cc=zsh-workers@math.gatech.edu \
    /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).