I get this error when I try to use SLIME with SBCL:
Lisp connection closed unexpectedly: connection broken by remote peer
That is the Emacs message. In the *inferior-lisp* buffer, this is displayed:
--
WARNING: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING CALLS-WHO DISASSEMBLE-FRAME INSPECT-FOR-EMACS SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) T * ;; Swank started at port: 32794.
NIL * Process inferior-lisp hangup
--
I load slime with a small function of mine:
(defun slime-load () (interactive) (add-to-list 'load-path "~/pgm/slime/") ; your SLIME directory ;; (setq inferior-lisp-program "/usr/bin/clisp") ; your Lisp system (setq inferior-lisp-program "/usr/local/bin/sbcl") ; your Lisp system (require 'slime) (slime-setup))
As you can see, I have used CLISP too, and that works (I changed the inferior-lisp-program variable just now and tested).
What could be the problem here?
When Googling I mostly found issues with sbcl running remotely, which is not an issue in my case.
Thanks!
/Mathias
Mathias Dahl brakjoller@gmail.com writes:
I get this error when I try to use SLIME with SBCL:
Lisp connection closed unexpectedly: connection broken by remote peer
Sorry, forgot the versions:
- GNU Emacs 22.0.50.26, running under Mandrake GNU/Linux.
- SBCL 0.9.13
- SLIME - not sure. The latest ChangeLog entry is from 2006-04-13.
/Mathias
Mathias Dahl brakjoller@gmail.com writes:
Mathias Dahl brakjoller@gmail.com writes:
I get this error when I try to use SLIME with SBCL:
Lisp connection closed unexpectedly: connection broken by remote peer
Sorry, forgot the versions:
- GNU Emacs 22.0.50.26, running under Mandrake GNU/Linux.
In the past, the sbcl hangup has been caused by a kernel problem. You can work around it by starting sbcl as "nohup sbcl" instead of plain "sbcl". Upgrading to a more recent kernel may also fix the problem for you.
Zach
Zach Beane xach@xach.com writes:
In the past, the sbcl hangup has been caused by a kernel problem. You can work around it by starting sbcl as "nohup sbcl" instead of plain "sbcl". Upgrading to a more recent kernel may also fix the problem for you.
I did C-u M-x slime RET (I noticed that I could use a prefix argument by reading the source). Then at the prompt I got I prepended "nohup" before the program (/usr/local/bin/sbcl in my case). It worked!
Will there be any bad side effects from doing this (using nohup) or can I expect it to work whatever I want to do?