Version 1.49 works fine, but 1.50 (and 1.51) gives me this when I start Slime:
---8<--- (From *Messages* and the Slime-repl:) Polling "/tmp/slime.8009".. (Abort with `M-x slime-disconnect'.) [2 times] Connecting to Swank on port 41288.. Disconnected. error in process filter: slime-state/event-panic: The SLIME protocol reached an inconsistent state. error in process filter: The SLIME protocol reached an inconsistent state.
The event was: (:new-features ("ASDF" "MK-DEFSYSTEM" "COMMON-LISP-CONTROLLER" "PCL-STRUCTURES" "PORTABLE-COMMONLOOPS" "PCL" "PYTHON" "PENTIUM" "I486" "LINKAGE-TABLE" "MP" "GENCGC" "CMU18" "CMU18E" "RELATIVE-PACKAGE-NAMES" "CONSERVATIVE-FLOAT-TYPE" "RANDOM-MT19937" "HASH-NEW" "X86" "LINUX" "GLIBC2" "UNIX" "COMMON" "CMU" "NEW-COMPILER" "COMMON-LISP" "ANSI-CL" "IEEE-FLOATING-POINT"))
The state stack was: (slime-evaluating-state slime-idle-state) ---8<---
This is with Emacs 21.3+1-4 and CMUCL 18e-7 on Debian.
Johannes Groedem johs+n@ifi.uio.no writes:
Version 1.49 works fine, but 1.50 (and 1.51) gives me this when I start Slime:
It looks like your slime.el and swank.lisp are out of sync. In particular, the `:new-features' message is a protocol extension that was added to both sides the other day.
Maybe you have an out-of-date byte compiled copy of slime.el or something?
Cheers, Luke
* Luke Gorrie luke@bluetail.com:
Maybe you have an out-of-date byte compiled copy of slime.el or something?
I deleted the byte compiled copy when I updated. Um, but now it works, somehow, so I guess I must have fucked up something. Sorry.
Luke Gorrie writes:
Maybe you have an out-of-date byte compiled copy of slime.el or something?
By the way, can slime.el be compiled? Since README doesn't mention this, and there is apparently no automated build procedure like that for .lisp files, I assumed that it shouldn't.
Paolo
Paolo Amoroso amoroso@mclink.it writes:
Luke Gorrie writes:
Maybe you have an out-of-date byte compiled copy of slime.el or something?
By the way, can slime.el be compiled? Since README doesn't mention this, and there is apparently no automated build procedure like that for .lisp files, I assumed that it shouldn't.
It should be okay to byte-compile - if not it's a bug. I just did a little tweaking and it seems to work for me. I don't usually do this, because when I byte-compile I always end up with troubles like Johannes had.
Byte-compiling did flush out some bugs embarrassing bugs that I fixed on the way past - so I'll do it more often :-)
-Luke
-
Johannes Groedem -
Luke Gorrie -
Paolo Amoroso