Migrate mason-lspconfig handlers to vim.lsp.config #1743
Conversation
|
If I understand this correctly, all config settings that are currently (so, before this fix) set within @tjdevries, if that is correct, any chance we can merge this to prevent other starters from going crazy, as their LSP configs are never applied? Thank you for the project & the fix ❤️ |
|
I spent way too long realizing this was the reason my attempts to fix an issue with ElixirLS seemed to have no effect at all :( |
For the discussion nvim-lua#1475 and for the actual change nvim-lua#1743
| -- by the server configuration above. Useful when disabling | ||
| -- certain features of an LSP (for example, turning off formatting for ts_ls) | ||
| config.capabilities = vim.tbl_deep_extend('force', {}, capabilities, config.capabilities or {}) | ||
| vim.lsp.config(name, config) |
There was a problem hiding this comment.
I think this is missing one line as mentioned here. Without this change the LSP does not start automatically when a file is opened.
| vim.lsp.config(name, config) | |
| vim.lsp.config(name, config) | |
| vim.lsp.enable(name) |
4 participants
As stated in the
mason-lspconfigchangelog, they removed thehandlersconfiguration in their plugin, making Kickstart no longer responsible for automatic LSP server configuration.