Xref: utzoo comp.emacs:8364 gnu.emacs:2904 comp.unix.i386:5341
Path: utzoo!attcan!uunet!samsung!emory!hubcap!ncrcae!ncr-sd!rancho!rock
From: rock@rancho.uucp (Rock Kent)
Newsgroups: comp.emacs,gnu.emacs,comp.unix.i386
Subject: GNUemacs Murder-Suicide under BASH
Summary: emacs kill bash upon ^G
Keywords: GNU emacs bash fatal error
Message-ID: <1990May26.054523.19453@rancho.uucp>
Date: 26 May 90 05:45:23 GMT
Organization: Del Rayo Ranch, San Diego, CA
Lines: 19

I have GNU Emacs 18.55 running under BASH version 1.05 on an 80386
machine running System V Release 3.  

While I'm happy with them individually, they have an aggravating habit
when working together.  The first time I hit ^G in emacs in order to
abort an extended command everything is OK.  The second time, though,
a signal is somehow passed on the bash causing both emacs and bash to
terminate leaving only the message "Fatal error (1).".  

If you've encountered and solved this problem, I would really
appreciate some pointers.  My fingers, having spent considerable time
in adjusting autonomic reactions to the demands of emacs, are too
often getting to the ^G before my brain can intervene.  :-)

Thanks.

***************************************************************************
*Rock Kent    rock@rancho.uucp        POB 8964, Rancho Sante Fe, CA. 92067*
***************************************************************************