On 2010-12-29, at 4:35 PM, Matthew Mondor wrote:
On Wed, 29 Dec 2010 15:56:46 -0500 Philippe Sismondi psismondi@arqux.com wrote:
I can get along with this just fine. The only puzzling thing is why the recent versions of slime do not work properly on Ubuntu 10.10. That is perhaps for another thread, though, since my remote connection problems are solved.
It is possible that a default global emacs configuration, or your ~/.emacs, configures/starts slime in a way which used to work with an older slime but which must be adapted for a new slime. Also, if you updated slime, it might be good to delete/move the old FASL files (usually in ~/.slime/fasl/) so that it rebuilds from scratch
Thanks, Matthew.
I have routinely been deleting the contents of the .slime folder.
This is my .emacs file for the setup in which slime misbehaves:
(setq inferior-lisp-program "ccl") ;(add-to-list 'load-path "~/library/lisp/slime/") (add-to-list 'load-path "~/.local/share/common-lisp/source/slime") (require 'slime) (slime-setup)
The version in ~/.local/share/common-lisp/source/slime is the one that DOES NOT work properly with emacs locally in Ubuntu. The version of swank in that same directory DOES work to set up a swank server to which I connect in OS X, and is the same version as is present on OS X. You may recognize the directory as the default directory for asdf2 systems.
It is clear from the contents of the *inferior-lisp* buffer in Ubuntu emacs that this is the version of slime that is getting loaded.
Is there some other slime-specific or emacs configuration that could have an effect here? Would output from *inferiour-lisp* or *slime-events* tell us anything?
Best,
- Phil -