Question 1

How do I migrate from the old lspconfig setup to vim.lsp.config?

Accepted Answer

Upgrade to Neovim 0.11+, replace `require('lspconfig').setup{}` calls with `vim.lsp.config()` for customizations and `vim.lsp.enable()` to activate servers. Refer to the README's migration instructions for detailed steps.

Question 2

nvim-lspconfig vs coc.nvim: which is better for LSP in Neovim?

Accepted Answer

nvim-lspconfig is lighter and integrates directly with Neovim's native LSP, ideal for minimalists. coc.nvim is a more feature-rich extension host but adds overhead; choose based on whether you prioritize native integration or extended functionality.

Question 3

Why isn't my language server starting in Neovim with nvim-lspconfig?

Accepted Answer

Run `:checkhealth vim.lsp` to troubleshoot. Common issues include the server not being installed on your PATH, incorrect filetype detection, or missing root markers for workspace detection as specified in the configs.

Question 4

How can I add a custom language server configuration not in nvim-lspconfig?

Accepted Answer

Create a Lua file in `after/lsp/` on your runtimepath or use `vim.lsp.config()` to define a new config with the server's command and settings. Then enable it with `vim.lsp.enable()` to activate.

Question 5

Does nvim-lspconfig work with Neovim 0.10?

Accepted Answer

Support for Neovim 0.10 is being removed; you need to upgrade to 0.11.3 or higher. Using older versions may result in warnings, errors, and lack of future updates.

Question 6

How to get auto-completion for LSP server settings in my Neovim config?

Accepted Answer

Use the type annotations provided by nvim-lspconfig by adding `---@type lspconfig.settings.server_name` comments in your Lua configs, which leverages generated type definitions for editor support.

nvim-lspconfig

What is nvim-lspconfig?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions