Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Which slime-js version should I be using? #34

Closed
jxa opened this Issue · 15 comments

6 participants

@jxa
jxa commented

It is confusing to me that you have 2 versions of slime-js.el. One in the https://github.com/swank-js/slime-js repo and another in this repo. Which will be maintained going forward? Which should I be using now?

@Gozala
Owner

That's a good point, I moved slime-js before to it's own repo and published it to http://marmalade-repo.org/packages/slime-js so users could install it right from emacs without manual configs. Is there any reason @ivan4th @jonnay we're keeping copy here as well ?

@jonnay jonnay was assigned
@jonnay
Owner

K, I will make sure versions are in sync and then kill from the swank-js repo.

@ivan4th
Owner

Sorry, as I wrote before marmalade repo has very old version of SLIME. swank-js is no longer compatible with it...

@ivan4th
Owner

SLIME protocol was changed several times since April 2010, so in order to be able to use marmalade version we need to get newer SLIME there somehow

@Gozala
Owner

Sorry, as I wrote before marmalade repo has very old version of SLIME. swank-js is no longer compatible with it...

That's strange I have installed slime from marmalade and it's 20100404.1 and seems to work just fine with slime-js / swank-js as is.

@jxa
jxa commented
@ivan4th
Owner

I must confess my Emacs config is still collection of my own and others' elisp files lying around. I didn't get around to learning any Emacs packaging system yet, so I'm not an expert in this area. As of older SLIME compatibility, maybe older SLIME can accept new style connection info, but it will almost definitely choke on any non-ascii chars due to header encoding changes, as now SLIME message headers have their length field represented in bytes and not chars as in earlier SLIME versions.

@jonnay
Owner

Looking at MELPA, that seems like a reasonable way forward.

I don't have permission to fork the MELPA repository to swank.js. Can you give me permission? (or just do it). Once that is done, I can see about writing a MELPA recipe, and update the documentation.

The repo is here: https://github.com/milkypostman/melpa

@Gozala
Owner

It looks like version in MELPA either is broken or not compatible with swank-js. I get

slime-busy-p: Symbol's value as variable is void: --cl-accu--

Every time I try slime-connect with swank-js and also with clojure swank.

@capitaomorte

I had the same --cl-accu-- problem. There's something fishy here becauseI fixed by making sure I did not byte-compile slime.

@capitaomorte

The --cl-accu-- problem is apparently between the latest slime and emacs 24.1, it breaks for common lisp as well for example. http://stackoverflow.com/questions/9161871/slime-doesnt-work-in-emacs24 describes a possible fix.

@ajsharp

@capitaomorte thank you for this link, I finally fixed this issue!

@jonnay
Owner

Marking this as closed, as the --cl-accu-- problem doesn't seem to happen anymore, and slime-js.el is in its proper spot.

@jonnay jonnay closed this
@capitaomorte

The problem will still happen with any Emacs 24.1 but only if you byte-compile slime.el. Another problem, also related to lexical-binding being immature in versions prior to 24.3, is that not byte-compiling slime-presentations.el will produce an annoying error. Everything should be fine with Emacs 24.3. See the slime issue tracker for updates on these bugs.

@jonnay
Owner

Thanks @capitaomorte!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.