Path: utzoo!utgpu!watmath!iuvax!cica!tut.cis.ohio-state.edu!fulcrum.british-telecom.co.uk!igb
From: igb@fulcrum.british-telecom.co.uk (Ian G Batten)
Newsgroups: gnu.bash.bug
Subject: SIGINT and bash on Sys5
Message-ID: <13695.8908021336@holly.fulcrum.bt.co.uk>
Date: 2 Aug 89 13:36:59 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 21


I reported earlier today an interaction between Emacs and Bash on System V.
We investigated further and found the problem occurred with all SIGINTs.
If multiple shells were run from each other and then ``cat'' was run, a
Control-C to cat got a prompt from EACH shell stacked up and possibly
killed the top one.

[Parenthetically, I did a symptomatic patch to emacs by only using SIGQUIT
for ^G handling, rather than SIGQUIT and SIGINTR.  This is harmless, and
I may suggest it to the emacs maintainers].

Because a SIGINT will be delivered to all processes associated with the
terminal, the behaviour above is reasonable.  I have set the handler for
SIGINT to SIG_IGN on the parent side, and reset it later, around the 
wait in nojobs.  This fixes the immediate problem, and allows vi etc
to work, but I suspect  it will cause more problems.

This is bash 1.02 on V.3.2.  I'd like to hear from other people using bash
on S5.

ian