Much like in the recent thread on ssh, I'm trying to use Slime by connecting to a running Lisp. In theory, this ought to be simpler, because I'm not using ssh for it. I am not having much luck.
I'm using the latest CVS version of Slime (just ran an update and repeated my test); OpenMCL 1.14.3; and the Emacs version:
GNU Emacs 21.3.50.1 (powerpc-apple-darwin7.3.0) of 2004-05-08 on iBook.local
In the host process, I load Slime through asdf, then I start it by invoking
(setq swank:*use-dedicated-output-stream* nil) (swank:create-server :port 9090 :dont-close t :style nil)
The *use-dedicated-output-stream* is there because an old thread on this list advised it. I have also tried without the :style parameter, not that that should have any relevance.
Then in Emacs, I do M-x slime-connect RET 127.0.0.1 RET 9090 RET. Emacs says this:
Connecting to Swank on port 9090.. net-read error: (end-of-file) error in process-filter: byte-code: PANIC! error in process-filter: PANIC!
Lisp says this (I have it set up to dump into syslog):
;; Connection to Emacs lost. ;; [Short read: length=3158064 pos=58]
If I try to connect again, I get the same error messages on both ends, so at least I know the loop isn't falling through...
Both processes happen to be on the same computer, but are using different copies of the same version of Slime (one of them is inside a .app bundle...), in case that's relevant.
Please advise?
-- Dan Knapp
Dan Knapp dk-apple@accela.net writes:
In the host process, I load Slime through asdf, then I start it by invoking
(setq swank:*use-dedicated-output-stream* nil) (swank:create-server :port 9090 :dont-close t :style nil)
So far, so good. The style argument isn't needed, but shouldn't prevent SLIME from working.
;; Connection to Emacs lost. ;; [Short read: length=3158064 pos=58]
[...]
Both processes happen to be on the same computer, but are using different copies of the same version of Slime (one of them is inside a .app bundle...), in case that's relevant.
Are you sure they are the same version? The error message looks as if one end is using an old version of the protocol.
Helmut.
PS: Please switch the autowrap feature of your mail reader off. Your message is formatted badly; it's hard to read.
In the host process, I load Slime through asdf, then I start it by invoking
(setq swank:*use-dedicated-output-stream* nil) (swank:create-server :port 9090 :dont-close t :style nil)
So far, so good. The style argument isn't needed, but shouldn't prevent SLIME from working.
I have also tested without the style argument, without *use-dedicated-output-stream*, and with neither.
Are you sure they are the same version? The error message looks as if one end is using an old version of the protocol.
Well, I double-checked by temporarily replacing the copy that wasn't in the bundle with a symlink to the copy that was (suitable for testing but not deployment). I also cleaned out all the .dfsl files in ~/.slime/, in case any of them were stale. So they should be running from the same directory tree now. It still gave the same error.
-- Dan Knapp
-
Dan Knapp -
Helmut Eller