Hi.
I've downloaded SLIME from CVS, edited my .emacs as per the README file, and I can now use SLIME. It's great! :)
There is a bit of a nag though. When I type M-x cmulisp RET, I get the error message "Key sequence C-c C-v ] uses invalid prefix characters". Only after typing M-x cmulisp RET the second time will CMUCL actually start. And then I can do M-x slime RET and all is well.
I didn't get this behaviour with ILISP, so I think it's SLIME's doing. I thought it might have something to do with my GNU Emacs being a CVS version (21.3.50.2), but it happens in 21.3.1 as well. Also, there was a previous message on this list with a similar error message: http://article.gmane.org/gmane.lisp.slime.devel/227/
I've attached the debug output GNU Emacs generates. Any idea what's going on?
BTW, I'm using Debian GNU/Linux unstable with XFree86 4.3.0 and GNOME 2.4, if it makes any difference. (GNU Emacs with Gtk+ 2 support is great. :))
Regards,
Dirk Gerrits
Dirk Gerrits dirk@dirkgerrits.com writes:
There is a bit of a nag though. When I type M-x cmulisp RET, I get the error message "Key sequence C-c C-v ] uses invalid prefix characters". Only after typing M-x cmulisp RET the second time will CMUCL actually start. And then I can do M-x slime RET and all is well.
I think this is ILISP. Do you still get the problem if you take ILISP out of your load-path and just use `M-x slime' instead of `M-x cmulisp'? (Note: `cmulisp' is an ILISP command; we use `slime', optionally with a C-u prefix if you want to say how Lisp is to be started.)
You probably don't want to run SLIME and ILISP simultaneously. I take ILISP out of my load-path while using SLIME, since if you start ILISP it will attach itself to your lisp-mode-map forevermore and clash/merge unpredictably with SLIME.
-Luke
Luke Gorrie wrote:
Dirk Gerrits dirk@dirkgerrits.com writes:
There is a bit of a nag though. When I type M-x cmulisp RET, I get the error message "Key sequence C-c C-v ] uses invalid prefix characters". Only after typing M-x cmulisp RET the second time will CMUCL actually start. And then I can do M-x slime RET and all is well.
I think this is ILISP. Do you still get the problem if you take ILISP out of your load-path and just use `M-x slime' instead of `M-x cmulisp'? (Note: `cmulisp' is an ILISP command; we use `slime', optionally with a C-u prefix if you want to say how Lisp is to be started.)
You probably don't want to run SLIME and ILISP simultaneously. I take ILISP out of my load-path while using SLIME, since if you start ILISP it will attach itself to your lisp-mode-map forevermore and clash/merge unpredictably with SLIME.
Ah right. Using M-x slime RET indeed starts everything right away. Thanks!
It does however produce a small (wrong-type-argument stringp nil) error, before carrying on. I've deinstalled ILISP now, which fixes that, but it might be something to keep in mind for other Debian users. Installing ILISP through APT puts ILISP in your load-path. I don't know if you can change that without being root.
Regards,
Dirk Gerrits
Debugger entered--Lisp error: (wrong-type-argument stringp nil) looking-at(nil) hs-hide-block-at-point() slime-log-event((:%apply "slime-open-stream-to-lisp" (34369))) slime-dispatch-event((:%apply "slime-open-stream-to-lisp" (34369))) slime-process-available-input() slime-net-filter(#<process SLIME Lisp> ".(:%apply "slime-open-stream-to-lisp" (34369))\n")
-
Dirk Gerrits -
Luke Gorrie