Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Inconsistent signal handling?
- X-seq: zsh-workers 17902
- From: Philippe Troin <phil@xxxxxxxx>
- To: Peter Stephenson <pws@xxxxxxx>
- Subject: Re: Inconsistent signal handling?
- Date: 04 Nov 2002 11:22:23 -0800
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <29890.1036418650@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <29890.1036418650@xxxxxxx>
- Sender: Philippe Troin <phil@xxxxxxxx>
Peter Stephenson <pws@xxxxxxx> writes:
> Philippe Troin wrote:
> > [1] Why do we ignore SIGTERM on interactive sessions? That sounds
> > like a bad idea to me.
>
> We restore SIGTERM to the default in entersubsh(), i.e. for all spawned
> programmes. So the intent seems to be that only the parent shell
> ignores it.
Yes, I've never said that programs launched by zsh had SIGTERM blocked
or ignored. But I was wondering what was the rationale behind ignoring
SIGTERM within zsh? I've always been annoyed at not being able to kill
zsh with SIGTERM and having to send SIGHUP (or whatever-signal-of-the-day).
BTW what is your opinion about the rest of the patch?
Phil.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author