Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: signal weirdness
- X-seq: zsh-workers 2401
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Zefram <zefram@xxxxxxxxxxxxxxxxx>
- Subject: Re: signal weirdness
- Date: Wed, 13 Nov 1996 10:32:08 -0800
- Cc: zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: Zefram <zefram@xxxxxxxxxxxxxxxxx> "Re: signal weirdness" (Nov 13, 6:03pm)
- References: <26092.199611131803@xxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author