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

Unable to activate lsp-docker #2877

Open
pedz opened this issue Oct 5, 2022 · 0 comments
Open

Unable to activate lsp-docker #2877

pedz opened this issue Oct 5, 2022 · 0 comments

Comments

@pedz
Copy link
Contributor

pedz commented Oct 5, 2022

This might be pilot error...

I wanted to use lsp-docker but there was not an el-get recipe for it so I did el-get-elpa-build-local-recipes into /Users/pedz/.config/emacs/el-get/el-get/recipes/elpa. This path is in el-get-recipe-path and it is also the value of el-get-recipe-path-elpa. That might be where I went wrong...

After creating the elpa recipes, I used el-get-list-packages to install lsp-docker and other packages (like lsp-mode). I did this last week sometime.

Today, I noticed that at start up I was getting two errors. This is from memory but roughly they were

Unable to activate lsp-docker
dash-1.14.1 unavailable

In /Users/pedz/.config/emacs/elpa/lsp-docker-20220513.1434/lsp-docker-pkg.el is a requirement for this package.

In list-packages, lsp-docker was marked as installed. I tried installing dash via list-packages but then I got the error that dash was being loaded twice. After poking at it for some time, I finally moved my el-get setup into /Users/pedz/.config/emacs/early-init.el and now el-get is loading up everything before package-activate-all and package-activate-all sees that everything is loaded and does nothing.

One weird thing that seems broken is I installed the proper dash via list-packages and tried three times to delete dash from el-get-list-packages but each time upon restart, el-get would reload dash and then complain that it was being loaded twice.

Otherwise... now that I know about early-init.el, that seems as good a place to put the initialization of el-get as anywhere else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant