Closed spacebat closed 8 years ago
I've seen this before. You must be absolutely sure you have deleted stale .elc
files from earlier versions of SLY (including contribs!), where that data structure was slightly different.
But I will look closely to your report later.
Thanks, I had neglected to make clean
, and that fixed it. I forgot to mention it was accompanied by a client-server version mismatch warning, of course caused by old elc files. I'll close this now, but I wonder if you have any advice on making sly and slime coexist peacefully? Its going to be a while before I could use sly exclusively.
you have any advice on making sly and slime coexist peacefully
@spacebat, depends on what you mean. First of all, this particular problem was not caused by any SLY-SLIME interaction, rather two different SLY versions whose .elc files are incompatible between each other.
Regarding SLY-SLIME co-existance:
lisp-mode
for instance. It's as if you have two python modes (and there are at least couple of them) and try to activate them at the same time: it just doesn't make sense.
I've checked out sly master, compiled the contrib modules with
make compile compile-contrib
and deleted the contents of ~/.cache/common-lisp/Then I created a file init-sly.el with just the three lines for setup described in the sly readme - load-path, autoloads and inferior-lisp-program. Starting emacs with
emacs -q --load init-sly.el
and then running M-x sly, I get a wrong-type-argument error, because cl-second is being called on a string. This is becausesly-contrib--required-slynk-modules
is filled with conses such as:Whereas the documentation for this variable indicates the cdr of the items should be a list not a string. I've tried adding a message to the place where cl-pushnew is used to populate this alist, however it doesn't seem to be called - at least the messages don't appear in the Messages buffer.
This is the full backtrace I'm getting. Should I be checking out a tag instead of master?