Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • So this setup worked for Clojure with slime, but did not for the clisp slime integration. Somehow when I say M-x slime-common-lisp, it's still using slime from elpa. How do I fix that? Commented Dec 29, 2010 at 19:30
  • Try restarting Emacs before using M-x slime-common-lisp. An Emacs wizard would probably be able to say how to unload the ELPA SLIME before loading the CVS one but I don't know how to do it. Commented Dec 29, 2010 at 19:51
  • Yeah I did restart emacs before I tried M-x slime-common-lisp. However the ESK is loading the elpa/slime* before my slime-cvs one and hence the problem. I'll try asking on esk issues too. Thanks. Commented Dec 29, 2010 at 19:59
  • Report back! I struggled with this and might not have taken as close notes as I should have. It seems to work for me but maybe there's something else I did. Commented Dec 29, 2010 at 20:50
  • Ok I took a look at my setup tonight after work and updated my answer. What I did differently was to download the ELPA version of SLIME and then put that somewhere separate, unmanaged by the ELPA that comes with emacs-starter-kit. This is a pretty fragile set up, since if swank-clojure requires a newer version of SLIME and ELPA is updated, you'd have to fix this, so it will require a little baby sitting. On the other hand, I've read that ELPA is being neglected until then next major release of Emacs, so it might be safe for a while. Good luck, and let me know if it works for you! Commented Dec 30, 2010 at 3:17