Xref: utzoo comp.emacs:2851 comp.lang.lisp:735
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!csli!rustcat
From: rustcat@csli.STANFORD.EDU (Vallury Prabhakar)
Newsgroups: comp.emacs,comp.lang.lisp
Subject: Gnuemacs and Common Lisp
Message-ID: <2492@csli.STANFORD.EDU>
Date: 22 Feb 88 22:20:49 GMT
Reply-To: rustcat@russell.stanford.edu (Vallury Prabhakar)
Organization: Yonder, the Apocalyptic Horizons
Lines: 26
Keywords: Inferior shells, common lisp, gnuemacs

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.  

Has this happened to anyone else? Could it be a bug in any of the above
or something?  This is rather frustrating, because I'd like to save the
output of the Lisp-interpreter buffer into a file, and if Emacs keeps
choking everytime I call up lisp, then I obviously can't do that.

I'd appreciate any advice/suggestions that the gurus of netland might
have in this matter.  Here are the details:

Lisp:	Both KCL and Lucid produce the same results.  I use only Common Lisp
Machine: Sun/3/160.
OS:	4.2BSD
Emacs:  (GNUEmacs) Version 18.50.1

Thank you.

						-- Vallury Prabhakar

--
rustcat@cnc-sun.stanford.edu