[slime-devel] Re: Current way to use multiple lisp implementations?
peter at gigamonkeys.com
Sun Oct 30 21:56:41 UTC 2005
Helmut Eller <heller at common-lisp.net> writes:
> * Bill Clementson [2005-10-25 00:32+0200] writes:
>> This more recent message explains the current 'right' way:
> It changed again a little since then. I renamed the variable to
> slime-lisp-implementations and if that variable is non-nil then the
> first entry is used for `M-x slime'. If slime-lisp-implementations is
> nil, inferior-lisp-program is used as default.
> `M-- M-x slime' can be used to select another entry from
> slime-lisp-implementations. `C-u M-x slime' can still be used to
> interactively specify the command.
> For example:
> (setq slime-lisp-implementations
> '((cmucl ("/opt/cmucl/bin/lisp"))
> (acl-mule ("acl7") :coding-system emacs-mule-unix)
> (clisp ("clisp" "-q"))
> (xclisp ("clisp" "-q" "-M" "/tmp/x.mem")
> :init (lambda (file _)
> (format "(swank:start-server %S)\n\n" file)))))
> and cmucl will be used as default.
So I just synced up to head and adapted by slime config to use this
new mechanism. I'm sad to see that the slime buffer name is no longer
based on the symbolic name of the lisp implementation choosen. That
is, given this:
I'd hope that doing C-u - M-x slime acl8 would create a buffer named:
*slime-repl acl8*. Instead it creates *slime-repl allegro*. And then
if I create another connection using acl7 I get *slime-repl
allegro<2>* which is not so helpful. I just spent a few minutes poking
around trying to put back this feature but got lost--maybe someone
who's been dealing with this code more recently can put it back.
Peter Seibel * peter at gigamonkeys.com
Gigamonkeys Consulting * http://www.gigamonkeys.com/
Practical Common Lisp * http://www.gigamonkeys.com/book/
More information about the slime-devel