Hi. I'm having trouble with the above configuration. I saw this thread:
http://article.gmane.org/gmane.lisp.slime.devel/4367 http://article.gmane.org/gmane.lisp.slime.devel/4368
that looks like it might be the same or a related problem. I'm not really sure. Looked around the mailing list, did some web searching, I don't think this is a duplicate report.
Anyway, if I try to M-x slime with XEmacs-nomule (which is what I normally use) I get:
Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix bina
(cuts off, I don't know how to read more of the minibuffer) as an error.
If I try the mule version, which my distribution packages, I get a segmentation fault from XEmacs (this, of course, is probably better reported as an XEmacs bug, which I'm planning on doing.)
This is XEmacs 21.4.17 with slime cvs 20051202 and sbcl 0.9.7. This is my first time trying to start things up. (That is to say, I had no working previous configuration.)
I really don't know what to make of this, but here's what I get if I try it after setting debug-on-error to t:
Debugger entered--Lisp error: (error "Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)") signal(error ("Invalid slime-net-coding-system: nil. (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)")) cerror("Invalid slime-net-coding-system: %s. %s" nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)) apply(cerror "Invalid slime-net-coding-system: %s. %s" (nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix))) error("Invalid slime-net-coding-system: %s. %s" nil (iso-latin-1-unix iso-8859-1-unix binary utf-8-unix emacs-mule-unix euc-jp-unix)) (if props nil (error "Invalid slime-net-coding-system: %s. %s" coding-system (mapcar ... slime-net-valid-coding-systems))) (unless props (error "Invalid slime-net-coding-system: %s. %s" coding-system (mapcar ... slime-net-valid-coding-systems))) (let ((props ...)) (unless props (error "Invalid slime-net-coding-system: %s. %s" coding-system ...)) (when (and ... ...) (assert default-enable-multibyte-characters)) t) slime-check-coding-system(nil) (let ((args ...)) (slime-check-coding-system coding-system) (when (or ... ...) (let ... ... ...))) (catch (quote --cl-block-slime-start--) (let (...) (slime-check-coding-system coding-system) (when ... ...))) (cl-block-wrapper (catch (quote --cl-block-slime-start--) (let ... ... ...))) (block slime-start (let (...) (slime-check-coding-system coding-system) (when ... ...))) (let* ((program ...) (program-args ...) (coding-system ...) (init ...) (name ...) (buffer ...)) (let (...) (while --keys--102022 ...)) (block slime-start (let ... ... ...))) slime-start(:program "/usr/local/bin/sbcl" :program-args nil) apply(slime-start (:program "/usr/local/bin/sbcl" :program-args nil)) (lambda (&optional command coding-system) "Start an inferior^_superior Lisp and connect to its Swank server." (interactive) (apply (function slime-start) (slime-read-interactive-args)))() call-interactively(slime) command-execute(slime t) execute-extended-command(nil) call-interactively(execute-extended-command)
* Adam Fabian [2005-12-03 07:31+0100] writes:
I really don't know what to make of this, but here's what I get if I try it after setting debug-on-error to t:
Your XEmacs doesn't find any coding system, probably because we used check-coding-system to decide whether the coding system is available.
I rewrote that part a bit so that check-coding-system is only used if it's actually available.
If you still have problems, please report them because those coding-system things are terribly hard to get right in different Emacs versions.
Helmut Eller (who hates exotic coding-systems).
Well I still have problems with it, test on check-coding-system yiels true here but if it's called the coding system is not found.
Regards Friedrich