-
Notifications
You must be signed in to change notification settings - Fork 49
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 servers aren't installed on 7.3.1 #50
Comments
I don't trust the LSP installer plugin anymore. The upstream always abandons the old project and stops maintaining it. So I remove it in commit 564b780. Besides, managing that amount of the executable by an editor plugin is not suggested: the environment might be messed up by the plugin if they push some mistake to the master branch, and those prebuilt executable might got compatibility issues on your machine because they are built in the GitHub action (Incompatible glibc, share library...etc), and the last and the most important reason is that we cannot fully trust an executable file downloaded by an editor plugin. There have been many examples of supply chain security issues. So, I recommend you use your system package manager to install those LSP servers. Your system package manager is always a trusted and reliable source. They are born to install/upgrade/uninstall packages. In my opinion, I don't want another pip/npm-like plugin to introduce a great deal of uncertainty. If you still prefer "automatically setup", you can try mason.nvim. But, please rethink carefully. |
On the latest
master
with latest nightly neovim I have this custom.lua:custom.lua
Nvim Info
Nodejs versions are managed by asdf and for global it's set to 16.14.2.
LspInfo output:
The text was updated successfully, but these errors were encountered: