🚀 go-pugleaf

A colleague asks if there is a fix for this annoying (but harmless)
bug.

Background:
	emacs-version 19.25.2

	./configure decstation --with-gcc \
	      --x-includes=/usr/include/mit --run-in-place 

	ULTRIX V4.2A (Rev. 47) System #1: Tue Jul 21 10:26:56 EDT 1992
	UWS V4.2A (Rev. 420)


The bug:  I first start emacs by "emacs -q", open a buffer, and type
ESC ESC (setq inferior-lisp-process "cl")
M-x run-lisp

I'm now in a lisp buffer, and here is the session:

----------------------------------------------------------
Allegro CL 3.1.12 [DEC 3100] (3/30/90)
Copyright (C) 1985-1990, Franz Inc., Berkeley, CA, USA
<cl> (+ 2 2)

4 
<cl> (* 34 10)

340 
<cl> <cl> 
Error: Attempt to take the value of the unbound symbol <CL>
[1] <cl> 
-----------------------------------------------------------

I entered two sexps ( (+ 2 2) and (* 34 10)) and got the correct
answer. I now moved back to the line 

<cl> (* 34 10)

and pressed the RETURN key.  I got the above error.

The correct behavior is to evaluate the sexp on the line, but <cl> is
being passed to the interpreter, not the sexp.






Steve Fisk                              Department of Mathematics
207-725-3574                            Bowdoin College
fisk@bowdoin.edu                        Brunswick, Me. 04011 USA