When I quit CMUCL from *inferior-lisp* with `(quit)' I get the following message in the buffer:
Process inferior-lisp finished
and these messages in the echo area/minibuffer:
(Inferior Lisp:no process Inf-Slime[not connected]) Lisp connection closed:exited abnormally with code 256^J
Is this the expected behavior? My setup is: Debian Woody, GNU Emacs 20.7, CMUCL 18e, SLIME CVS sources updated half a dozen hours ago.
Paolo
P.S. I almost forgot: kudos!
Hi Paolo,
Sorry about my tardy reply. I seem to be losing some mail from slime-devel mysteriously. I only just realised, so I'm catching up via Gmane.
When I quit CMUCL from *inferior-lisp* with `(quit)' I get the following message in the buffer:
Process inferior-lisp finished
and these messages in the echo area/minibuffer:
(Inferior Lisp:no process Inf-Slime[not connected]) Lisp connection closed:exited abnormally with code 256^J
Is this the expected behavior? My setup is: Debian Woody, GNU Emacs 20.7, CMUCL 18e, SLIME CVS sources updated half a dozen hours ago.
Well, for some value of "expected". The "exited abnormally" message (which really means the socket was closed) is gratuitous here, so I've changed it to only be printed if the inferior-lisp is still running.
Cheers, Luke
Luke Gorrie lgorrie@nortelnetworks.com writes:
Sorry about my tardy reply. I seem to be losing some mail from slime-devel mysteriously. I only just realised, so I'm catching up via Gmane.
A word to the wise: don't run fetchmail in daemon mode with logging turned off. :-)
Turns out 250 "random" mails for me have been left on my POP server over the past month. A dozen of them weren't even spam.
-Luke
Luke Gorrie writes:
Well, for some value of "expected". The "exited abnormally" message (which really means the socket was closed) is gratuitous here, so I've changed it to only be printed if the inferior-lisp is still running.
It seems to work fine now.
Paolo
-
Luke Gorrie -
Paolo Amoroso