-
-
Notifications
You must be signed in to change notification settings - Fork 102
neovim/lsp: expose low-level API #860
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
Conversation
c262071
to
97044e6
Compare
✅ Preview has been deleted successfully! |
Note: this breaks if you're not on neovim 0.11.0+ as vim.lsp.config wasn't introduced until then. I found it as I'm on nix-stable-24.11 until 25.05 comes out, and that has neovim v0.10.2 still. Error from today:
neovim version:
|
Please do not override nvf's nixpkgs version. I know this can be (and should be) communicated better, but we only target nixpkgs unstable since we do not have the manpower to divert energy to supporting the stable branch. You can remove the |
This exposes a low(er) level API for configuring LSPs directly with the new
options provided by Neovim 0.11. The idea is to allow configuring LSPs without
relying on the inclusion of language modules into nvf, or allowing language
modules in user configurations.
The language modules still use the old API, and will be migrated in due time.
Changes here are split off to avoid withholding important additions to the
module system until all language modules are converted. Language modules, of
course, will still need to be converted to this new API, after which lspconfig
shall be made into a regular plugin module instead of its current, specially
treated "variant."
Related: #748