Xref: utzoo comp.emacs:2852 comp.lang.lisp:736
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!helman@isl.Stanford.EDU
From: helman@isl.Stanford.EDU (Jim Helman)
Newsgroups: comp.emacs,comp.lang.lisp
Subject: Re: Gnuemacs and Common Lisp
Message-ID: <106@isl.stanford.edu>
Date: 23 Feb 88 00:15:14 GMT
References: <2492@csli.STANFORD.EDU>
Reply-To: helman@isl.UUCP (Jim Helman)
Organization: Stanford University
Lines: 25
Keywords: Inferior shells, common lisp, gnuemacs

In article <2492@csli.STANFORD.EDU> rustcat@russell.stanford.edu (Vallury Prabhakar) writes:
>The way I normally work in the Lisp interpreter, is to fire up Gnuemacs
>then open up a sub-window to set up an inferior shell to run Lisp in.
>For some strange reason, this doesn't always seem to work.  Sometimes 
>it works just fine, and other times it just hangs.  All the interpreter
>seems to be able to recognize is when I type an invalid control character
>like ^C.  
>
>Emacs:  (GNUEmacs) Version 18.50.1

It appears that in release 18.50, lisp-mode.el was modified but
shell.el wasn't changed to make it compatible.  It may not be the same
problem, since inferior lisps weren't working at all for me.

I'm no emacs lisp hacker, but after changing line 390 of shell.el from:
 (lisp-mode-variables) 
to:
 (lisp-mode-variables nil)
it seems to work OK.  You'll also need to byte-compile the new
shell.el or explicitly load it, otherwise you'll still be loading the
old shell.elc file.

Jim Helman (jim@thrush.stanford.edu)
Department of Applied Physics
Stanford University