Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site loral.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcc6!loral!simard
From: simard@loral.UUCP (Ray Simard)
Newsgroups: net.emacs
Subject: emacs crash - appeal for ideas
Message-ID: <690@loral.UUCP>
Date: Mon, 3-Dec-84 22:23:01 EST
Article-I.D.: loral.690
Posted: Mon Dec  3 22:23:01 1984
Date-Received: Wed, 5-Dec-84 01:30:36 EST
Organization: Loral Instrumentation, San Diego, CA
Lines: 30


Hi there!

I have asked this before, but recevied no replies.  I'll try again.

Often, when a search-forward is executed and keys are accidentally
typed, emacs (Gosling flavor) goes inert for a long while, then
prints the message "Starting subshell" and does that.
Exiting or killing the shell locks up the terminal completely, requiring
killing emacs and/or the login shell from another terminal.  At that
time, often the checkpoint file contains such things as hunks of
the password file, or a list of my environment variables, and
other randomish garbage.  Sometimes the work is salvageable, and
sometimes not.

Any ideas as to why this happens, and how to avoid it (other than
the obvious "don't type keys while emacs is searching" ??

advTHANKSance

-- 

[     I am not a stranger, but a friend you haven't met yet     ]

Ray Simard
Loral Instrumentation, San Diego
{ucbvax, ittvax!dcdwest}!sdcsvax!sdcc6!loral!simard

...Though we may sometimes disagree,
   You are still a friend to me!