"Luke Gorrie" luke@synap.se wrote:
"Marc Battyani" marc.battyani@fractalconcept.com writes:
After slime-connect I have this: (:emacs-rex (swank:connection-info) nil t 1)
After Show REPL I have this added:
(:emacs-rex (swank:listener-eval "(+ 1 2)\n") "COMMON-LISP-USER" :repl-thread 2)
In both cases Emacs has sent an RPC request and Lisp hasn't responded.
Can you try (setq swank::*log-events* t) in the Lisp side before doing `slime-connect'? That way it will print protocol messages and we can see if it's successfully READ'ing those same messages we see logged in *slime-events*.
OK, I get this when I do slime-connect in XEmacs 21.5 beta18:
in LW 4.4: WRITE: (:open-dedicated-output-stream 1381)
in XEmacs: nil byte-code("..." [error message "net-read error: %S" ding sleep-for 2 debug nil (slime-net-close proc) ((error)) "PANIC!"] 3) slime-process-available-input() slime-net-filter(#<network connection "SLIME Lisp" (4005 . "127.0.0.1") state:run> "
It would also be interesting to see a backtrace for any SLIME threads, if that's easy to get. Edi's idea of testing in GNU Emacs would also be good if you happen to have it handy.
I tried with gnu Emacs 21.3.1 and got:
in LW: WRITE: (:open-dedicated-output-stream 1401)
in gnu Emacs: Debugger entered: nil byte-code("ÁÂ",HC(B ,HDÅ(B!,HF(B ,HGÈÉ,_ÀÊ(B!,G"(B [error message "net-read error: %S" ding sleep-for 2 debug G89685 (slime-net-close proc) ((error)) "PANIC!"] 3) slime-process-available-input() slime-net-filter(#<process SLIME Lisp> "
On the Lisp side I call this: (swank::create-swank-server 4005 :spawn #'swank::simple-announce-function t)
Marc