From: chuck@coplex.coplex.com (Chuck Sites) Subject: Re: ELM, nn, and emacs interaction problem after (ctrl-g) Date: Tue, 8 Jun 1993 03:16:47 GMT
dmcintyr@nyx.cs.du.edu (Doug McIntyre) writes:
>Christian.Kuehnke@arbi.informatik.uni-oldenburg.de (Christian Kuehnke) writes:
>>chuck@coplex.coplex.com (Chuck Sites) writes:
>>> I ran into a problem the other day that I havn't been able to
>>>resolve and I was hoping someone out there might have seen this.
>>>Using either elm or nn, if I want to reply followup etc, these
>>>programs call emacs (defined in the shell variable EDITOR=
>>>/usr/bin/emacs). This all is fine, except there seems to be a
>>>repeatable problem (atually a horrible problem) that when one types
>>>ctrl-g to abort a command under emacs, the calling program 'nn' or
>>>'elm' becomes activated. Apparently nn and elm traps this and wakes
>>>up, giving the confusing situation of having both programs running
>>>simultaniously with both trying to grab the same imput.
>>This is a known bug with signal handling in the bash and will
>>(according to the developers) be fixed in the next release.
> Thats all and well (and I've seen a half dozen bug fixes for bash),
>but the problem also happens under tcsh.. Now, one shell having a bug
>might be a possiblty, but under two of the most popular?
I've had several replies to my message that seem to indicate a
peculiarity with signal handling in the linux kernel. Not being
a kernel hacker type, I can't say. Anyway the patched version of
bash did solve the problem for me. My sanity has been saved!
For the benefit of others out there, the you can grab the fixed
binary version on susnite.unc.edu in /pub/Linux/system/Shells/
bash-1.12-fixed.tar.z
Thnaks for all the help,
Chuck Sites
chuck@coplex.com