Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!umcp-cs!chris From: chris@umcp-cs.UUCP (Chris Torek) Newsgroups: net.emacs Subject: Re: emacs crash - appeal for ideas Message-ID: <1665@umcp-cs.UUCP> Date: Thu, 6-Dec-84 20:40:09 EST Article-I.D.: umcp-cs.1665 Posted: Thu Dec 6 20:40:09 1984 Date-Received: Sat, 8-Dec-84 07:03:25 EST References: <690@loral.UUCP> Organization: U of Maryland, Computer Science Dept., College Park, MD Lines: 28 > 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. > Any ideas as to why this happens, and how to avoid it (other than > the obvious "don't type keys while emacs is searching" ?? In the keyboard reading code (probably in fill_chan or some variant thereof depending on whose mods you have) you fill find something like if (err) return; This is bogus; delete it. Your problems should vanish. (For anyone who cares, the problem is that there is a stdio-like structure holding an input character count and a pointer. If the character count was positive before a --, the next character from the pointed-to area is used, otherwise fill_chan is called. If fill_chan returns early (returning no particular value), interesting random things happen until err somehow gets cleared.) -- (This line accidently left nonblank.) In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (301) 454-7690 UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland