A few things:
1) How do I subscribe to slime-devel? I'm not sure that I have anything to contribute, but I like knowing what's going on :-)
2) swank-sbcl does
(require 'sb-bsd-sockets) and (require 'sb-introspect)
These are asdf packages, and require won't be able to find them unless asdf itself is in the SBCL image; in other words, they should be preceded by
(require 'asdf)
3) I've been seeing these errors (or something similar) for a few days now:
: You have encountered a bug in SLIME. : : The communication state machine received an event that was illegal for : its current state, which means that the communication between Emacs : and Lisp has lost synchronization. The connection to Lisp has : therefore been closed. : : You can open a fresh connection with `M-x slime'. : : Please report this problem to your friendly neighbourhood SLIME : hacker, or the mailing list at slime-devel@common-lisp.net. Please : include in your report: : : A description of what you were doing when the problem occured, : the version of SLIME, Emacs, and Lisp that you are using, : the Lisp backtrace, if one was printed, : and the information printed below: : : The event was: : (:new-features : ("ASDF" "ANSI-CL" "COMMON-LISP" "SBCL" "UNIX" "SB-DOC" "SB-TEST" "IEEE-FLOATING-POINT" "X86" "BSD" "FREEBSD" "GENCGC" "STACK-GROWS-DOWNWARD-NOT-UPWARD" "C-STACK-IS-CONTROL-STACK")) : : : The state stack was: : (slime-evaluating-state slime-idle-state)
Raymond Wiker Raymond.Wiker@fast.no writes:
A few things: 1) How do I subscribe to slime-devel? I'm not sure that I haveanything to contribute, but I like knowing what's going on :-)
You can subscribe to the mailing list via the web interface at http://common-lisp.net/mailman/listinfo/slime-devel. Alternatively, you can read via NNTP at news://news.gmane.org/gmane.lisp.slime.devel
2) swank-sbcl does (require 'sb-bsd-sockets)and (require 'sb-introspect)
These are asdf packages, and require won't be able to findthem unless asdf itself is in the SBCL image; in other words, they should be preceded by
(require 'asdf)
Apparently in more recent SBCLs ASDF will auto-load. Here's what Christophe Rhodes said:
http://common-lisp.net/pipermail/slime-devel/2003-October/000033.html
(Actually, that was in reply to an earlier mail from you, but it seems your address you fell off the CC-list.)
3) I've been seeing these errors (or something similar) for a fewdays now:
: You have encountered a bug in SLIME.
We had a similar report recently:
http://common-lisp.net/pipermail/slime-devel/2003-November/000070.html
It seems you're running an older version of the Elisp code that the CL backend that it talks to. Possibly there's an old byte-compiled slime.elc being loaded instead of the latest code?
Cheers, Luke
Luke Gorrie writes:
Raymond Wiker Raymond.Wiker@fast.no writes:
A few things: 1) How do I subscribe to slime-devel? I'm not sure that I haveanything to contribute, but I like knowing what's going on :-)
You can subscribe to the mailing list via the web interface at http://common-lisp.net/mailman/listinfo/slime-devel. Alternatively, you can read via NNTP at news://news.gmane.org/gmane.lisp.slime.devel
Ok!
2) swank-sbcl does (require 'sb-bsd-sockets)and (require 'sb-introspect)
These are asdf packages, and require won't be able to findthem unless asdf itself is in the SBCL image; in other words, they should be preceded by
(require 'asdf)Apparently in more recent SBCLs ASDF will auto-load. Here's what Christophe Rhodes said:
http://common-lisp.net/pipermail/slime-devel/2003-October/000033.html
Hum... that seems to be the case here, too... Does that mean I have a properly-installed SBCL? Joy!
(Actually, that was in reply to an earlier mail from you, but it seems your address you fell off the CC-list.)
3) I've been seeing these errors (or something similar) for a fewdays now:
: You have encountered a bug in SLIME.
We had a similar report recently:
http://common-lisp.net/pipermail/slime-devel/2003-November/000070.html
It seems you're running an older version of the Elisp code that the CL backend that it talks to. Possibly there's an old byte-compiled slime.elc being loaded instead of the latest code?
Yup. Could even be that I had forgotten to re-load slime; I'm in the habit of keeping my Emacs running for months. I started up a fresh XEmacs, and slime works like a charm.
Now that I have actually been able to play aound a little with SLIME, I have just one thing to say: AWESOME. I don't normally use font-lock, but I *may* have to start using it (with SLIME, at least).
-
Luke Gorrie -
Raymond Wiker