From fde0b487fb612e68de2ca11054560ca7f36c49b2 Mon Sep 17 00:00:00 2001 From: skewb1k Date: Tue, 16 Sep 2025 03:50:53 +0300 Subject: fix(lsp): avoid re-enabling `document_color` on `registerCapability` (#35774) Problem: The registerCapability handler re-enables document_color, making it impossible to disable it in LspAttach. Solution: Enable it once on initialization and avoid re-enabling on registerCapability. --- runtime/lua/vim/lsp/client.lua | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'runtime/lua/vim/lsp/client.lua') diff --git a/runtime/lua/vim/lsp/client.lua b/runtime/lua/vim/lsp/client.lua index 1b49d946e9..48b7ec17f9 100644 --- a/runtime/lua/vim/lsp/client.lua +++ b/runtime/lua/vim/lsp/client.lua @@ -1087,6 +1087,10 @@ function Client:on_attach(bufnr) self:_text_document_did_open_handler(bufnr) lsp._set_defaults(self, bufnr) + -- `enable(true)` cannot be called from `_set_defaults` for features with dynamic registration, + -- because it overrides the state every time `client/registerCapability` is received. + -- To allow disabling it once in `LspAttach`, we enable it once here instead. + lsp.document_color.enable(true, bufnr) api.nvim_exec_autocmds('LspAttach', { buffer = bufnr, -- cgit