-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M-x slime [No match] #808
Comments
You probably have figured this out yourself, but anyway, I think that version 2.29.1 of SLIME is obsolete - better to get the one from MELPA (20240125 is the latest, I think.) In your second |
2.29.1 is the latest version of Slime. I have never used melpa, but I've seen a lot of confusion from those who use it. |
@stassats thanks for the information. When I install SLIME (with MELPA enabled) I have a choice of
The nongnu version has a date of 2024-Jan-24 (reference) |
The elpa/melpa/whatever packages are maintained by someone (something) else. So I have no idea what they do. |
Understood, but literally item 1 in your quick setup instructions is "Set up the MELPA repository" As far as I can see, the nongnu ELPA version seems to have inexplicably omitted your I see there was some sort of beef with ELPA recorded here
and in the linked PR #648 Do you want me to try and contact that someone or something at ELPA because it would be good to have this working "out of the box"? I'm happy to give it a go! |
Part of the reason I don't understand or trust ELPA, why did they include code from some third party branch? And then can't remove it. I don't really want to be fixing their mistakes. |
No. I just got lucky when I decided to try the .emacs file from emacs4cl. I could see some differences in Here was the directory for the 29.2
Here is the directory for the 29.1
Here's
That's identical (except for the package names) to what was in my first .emacs file, and I assume custom.el gets read somehow just like .emacs. Okay, that's setup here:
I'm not sure what the point is of having both a .emacs file and a custom.el file. So, the main differences I see between the two emacs installs are package names like:
v.
|
For a new emacs user, what is your recommended method for installing packages, and specifically slime? |
I'm coming to the conclusion that this isn't the right place to complain; both MELPA and nongnu ELPA take the outputs of this project and package them in their own ways. MELPA updates theirs every time there's a new commit and ELPA take the github releases. At the moment, MELPA works and ELPA doesn't because they're modifying the github release tarball. (If I'm wrong about that, please someone correct me) So, if you want to get going today, use MELPA. In the meantime I will try and contact whoever is behind the ELPA and see if I can figure out why the difference and if it can be brought into sync, because I'd like slime to be working without this hassle! For reference, my
|
Is the "Source code(tar.gz)" from the release page really unusable? I, naturally, haven't tried using it. |
I haven't tried either (beyond looking at its contents) but I believe it would be usable - the one that isn't is nongnu ELPA (linked here) because they have removed In other words, normally the function If you install the ELPA package and cat I think that's correct - let me check it before we get any further though! |
A pull request with magic would be welcome. |
I've asked a question on the emacs mailing list (hopefully the right place) as I need a bit of guidance on fixing this |
Note that NonGNU ELPA doesn't modify any tarball, we use the last commit that bumps the version tag and use that as the basis to prepare a .tar package that is hosted by the archive. As part of that process, the ELPA build server generates an |
@phikal slime-autoloads.el was removed from emacs/nongnu.git in this commit: https://git.savannah.gnu.org/gitweb/?p=emacs/nongnu.git;a=commit;h=6e0d67b9b7ae0fc31902609ab7525826b292c384 |
I know, that is because they don't have to be tracked in the repository. |
The downside is that it will load slime as soon as emacs starts, whether you need it or not. What should happen is that emacs package manager loads slime-autoloads.el, which contains (effectively) a lightweight 'stub' of the slime function. All this does when called is to load the actual slime package, overwriting itself. Emacs will load quicker and with less memory usage because defers loading the actual package (which contains many functions) until the first time it's used, thereafter it will be just as if you'd require'd slime. This may not be a big deal to you; it can become significant if you've installed lots of packages - loading them all at startup would be slow. The problem here was that the slime-autoloads.el was wrong - it didn't even load the slime stub hence when you typed It should be fixed in ELPA after the next release, see #809 |
I installed
Emacs 29.2
andsbcl 2.4.0
onmacOS 12.51
with an Apple M1 Pro chip.Then I installed
slime
using the commandM-x package-install<Ret>slime<Ret>
. I can see that slime is installed:Now, I'm trying to get slime to work following these instructions:
In emacs, I opened a hello world
.lisp
file withC-x C-f
. However, when I typeM-x slime<Ret>
, I get[No match]
. Same forM-x slime-mode<Ret>
.Here is my
~/.emacs
file:sbcl
is in my path:I tried altering the .emacs file to use the full path to
sbcl
:but I still get
M-x slime [No match]
. I've been quitting emacs and relaunching it after I make changes to the.emacs
file.Here is my
~/.emacs.d/elpa
directory (which I haven't touched):There were a bunch of warnings when I installed slime:
I switched to another distribution with emacs 29.1, and I had the same problem. Then I tried using the .emacs file for emacs4cl with my emacs 29.1:
With that .emacs file,
M-x slime
successfully opened a window with the slime repl.The text was updated successfully, but these errors were encountered: