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

lsp update logic breaks functionality #11

Closed
laur89 opened this issue May 15, 2023 · 2 comments · Fixed by #13
Closed

lsp update logic breaks functionality #11

laur89 opened this issue May 15, 2023 · 2 comments · Fixed by #13

Comments

@laur89
Copy link
Contributor

laur89 commented May 15, 2023

coc-clojure had already been installed, and everything worked fine for a few days.
Now when opening a .clj file, the clojure-lsp is outdated. Download from Github? message started showing again. Selecting either choice closes the pop-up message but does nothing (ie clojure-lsp isn't updated nor are any errors shown) and no syntax errors are highlighted, suggesting the communication with lsp is broken.

If "clojure.lsp-check-on-start": false is set in ~/.config/nvim/coc-settings.json however, then the currently installed lsp works and syntax errors are shown.

How to proceed?


vim version: NVIM v0.7.2
node version: v19.5.0
coc.nvim version: 0.0.82-b7375d5f 2023-01-30 05:09:03 +0800
coc-clojure Current version 0.0.14

$ cat ~/.config/coc/extensions/coc-clojure-data/clojure-lsp-version
2023.05.04-19.38.01
@NoahTheDuke
Copy link
Owner

Uh oh! Thanks for letting me know. I'll take a look and see if I can get it fixed for you.

@laur89
Copy link
Contributor Author

laur89 commented May 31, 2023

Note it only breaks if LSP has already been downloaded. If you remove ~/.config/coc/extensions/coc-clojure-data/ (that's the default location), then the startup logic nicely pulls fresh version and everything works a-ok.

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

Successfully merging a pull request may close this issue.

2 participants