Skip to content
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

If emacs reports a version number with three digits, packages are not included in the load path #13

Closed
UndeadKernel opened this issue Oct 7, 2016 · 3 comments

Comments

@UndeadKernel
Copy link
Member

Due to a change in how the constant 'doom-packages-dir' is initialized, emacs versions with more than three numbers will not be able to load packages downloaded by cask.

The current version of emacs in Arch, for instance, is 25.1.1. In it's current state, cask packages fail to load.

@hlissner
Copy link
Member

hlissner commented Oct 7, 2016

I recall addressing this issue recently.

Here's the problem: in a recent update, Cask changed where it downloads plugins to:

It installs "bootstrap" packages to .cask/25.1.1/bootstrap, and installs the actual packages to .cask/25.1/elpa. I don't know why they made this change. It used to be all in the same folder (.cask/25.1.1/{elpa,bootstrap}/*). doom-packages-dir points to the right directory, but your plugins are likely in the old location.

So here are two solutions:

  1. Move the old packages to the new place:

    mkdir ~/.emacs.d/.cask/25.1
    mv ~/.emacs.d/.cask/25.1.1/elpa ~/.emacs.d/.cask/25.1/elpa
  2. Or reinstall your plugins with make install

Sorry about the sudden change! I don't even know if this is a bug on their end or intended behavior!

PS: I use Arch too! That's where I first discovered the issue.

@hlissner
Copy link
Member

hlissner commented Oct 7, 2016

Ah, I found the relevant commit in Cask. Looks like it was intentional.

@hlissner
Copy link
Member

hlissner commented Nov 4, 2016

I'll close this for now. I hope the above solution helped! Let me know if it didn't.

@hlissner hlissner closed this as completed Nov 4, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants