Remember when you first setup elpaca in your init.el and you copy+pasted a big block of elisp from elpaca's documentation? That elpaca setup code has a version-number variable that it sets. When you initialized your new Emacs instance, it installed elpaca from MELPA, but the version on MELPA is a newer version than your copy+pasted code from elpaca's docs. The solution is to replace your copy+pasted code by copy+pasting the new code in elpaca's docs.
this post was submitted on 29 Nov 2023
1 points (100.0% liked)
Emacs
311 readers
1 users here now
A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!
Get Emacs
Rules
- Posts should be emacs related
- Be kind please
- Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.
Emacs Resources
Emacs Tutorials
- Beginner’s Guide to Emacs
- Absolute Beginner's Guide to Emacs
- How to Learn Emacs: A Hand-drawn One-pager for Beginners
Useful Emacs configuration files and distributions
Quick pain-saver tip
founded 1 year ago
MODERATORS
[The Elpaca installer] has a version-number variable that it sets. [...] The solution is to replace [the installer with] the new code in elpaca's docs
This is correct. For anyone troubleshooting Elpaca, there is a Wiki which covers this warning.
When you initialized your new Emacs instance, it installed elpaca from MELPA
This is incorrect. The installer directly clones Elpaca. Elpaca is not hosted on any ELPA. Doing so would require an installer package to be installed by another package manager. I don't offer support for users running multiple package managers because it creates confusion about which package manager is responsible for which package, load-path entry, etc. MELPA rejected a similar proposal for straight.el as well:
https://github.com/melpa/melpa/issues/4939
cc: /u/liesdestroyer
This is incorrect. The installer directly clones Elpaca. Elpaca is not hosted on any ELPA. Doing so would require an installer package to be installed by another package manager.
Ah, right. That's obvious in hindsight, but I didn't give it much thought.
Thanks for the explanation, all is running smoothly
Yes, this. I've had this happen a number of times and the solution was just to bump the specified elpaca version. I've had no negative consequences from doing so.
Thank you so much! I didnt know