[slime-devel] Lisp connection closed unexpectedly

Plato Wu gtalk000 at gmail.com
Sun Dec 13 02:00:31 UTC 2009


Helmut Eller <heller at common-lisp.net> writes:

> * Plato Wu [2009-12-06 15:33+0100] writes:
>
>> I'm looking forward perfect solution, :)
>
> I sent a bug with a fix to the Emacs' maintainers:
> http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=5173
> but I haven't yet received an answer.
>
> In the meantime you can start Swank so that it accepts multiple
> connections which is opens a small security hole but has no other
> drawbacks.  You can achieve that if you put something like this in your
> .emacs:
>
> (defun load-swank-dont-close (port-filename encoding)
>   (format "%S\n\n"
> 	  `(progn
> 	     (load ,(expand-file-name slime-backend slime-path) :verbose t)
> 	     (funcall (read-from-string "swank-loader:init"))
> 	     (funcall (read-from-string "swank:start-server")
> 		      ,port-filename
> 		      :coding-system ,(slime-coding-system-cl-name encoding)
> 		      :dont-close t))))
>
> (setq slime-lisp-implementations
>       '((sbcl-noclose ("sbcl") :init load-swank-dont-close)))
>
> Helmut

Thanks, It works and hope Emacs's next release could accept your fix.





More information about the slime-devel mailing list