Hi all,
The latest Quicklisp update includes slime 2.4. It represents a big change from the previous dist, which used a CVS snapshot.
There have been two reports directly to me of SLIME not working after the update. In one case, the user reported that removing all instances of slime from ELPA fixed the problem. In another case, the report is:
starting SLIME results in "Symbol's function definition is void: slime-setup-contribs"
For me, after update, SLIME seems to start fine, but after typing anything in the REPL I get:
This `cl-labels' requires `lexical-binding' to be non-nil [6 times]
I'm using Emacs 24.2.1. Is that message to be expected and do I have to update my config to eliminate it?
What is the best way to discuss, troubleshoot, and fix these kinds of issues? Can they be discussed here on slime-devel?
Thanks, Zach
On Tue, Mar 18, 2014 at 1:25 PM, Zach Beane xach@xach.com wrote:
For me, after update, SLIME seems to start fine, but after typing anything in the REPL I get:
This `cl-labels' requires `lexical-binding' to be non-nil [6 times]
I'm using Emacs 24.2.1. Is that message to be expected and do I have to update my config to eliminate it?
That is a known issue for Emacs 24.1 and 24.2. (Things work fine with Emacs 24.3.) FWIW, there is a work-around described here: https://github.com/slime/slime/issues/122#issuecomment-36518247
What is the best way to discuss, troubleshoot, and fix these kinds of issues? Can they be discussed here on slime-devel?
The issue tracker at GitHub is a good place for reporting concrete bugs.
Luís Oliveira luismbo@gmail.com writes:
On Tue, Mar 18, 2014 at 1:25 PM, Zach Beane xach@xach.com wrote:
For me, after update, SLIME seems to start fine, but after typing anything in the REPL I get:
This `cl-labels' requires `lexical-binding' to be non-nil [6 times]
I'm using Emacs 24.2.1. Is that message to be expected and do I have to update my config to eliminate it?
That is a known issue for Emacs 24.1 and 24.2. (Things work fine with Emacs 24.3.) FWIW, there is a work-around described here: https://github.com/slime/slime/issues/122#issuecomment-36518247
What is the best way to discuss, troubleshoot, and fix these kinds of issues? Can they be discussed here on slime-devel?
The issue tracker at GitHub is a good place for reporting concrete bugs.
Ok, thanks.
So far the two issues have been resolved by removing non-2.4 slimes from the environment (one from ELPA, one from Aquamacs).
Zach