neovim

commit d3f5437542ab2acbced7120686a6c551e6072676
parent aeeadddac43b999a4bc6f57cbbdd2d7c7f1d08e4
Author: Calum Smith <hello@calum.io>
Date:   Thu, 16 Oct 2025 21:43:15 -0400

docs(lsp): specify exactly how `vim.lsp.config` merges configs (#36214)

docs(lsp): specify exactly how `vim.lsp.config` merges configs…

Problem:

It already says that the behaviour is defined by `vim.tbl_deep_extend`,
but that can mean very different things depending on the `behavior`
parameter.

Solution:

Specify that it uses "force".
Diffstat:
M
runtime/doc/lsp.txt
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/runtime/doc/lsp.txt b/runtime/doc/lsp.txt
@@ -157,8 +157,8 @@ EXAMPLE: DEFINE A CONFIG AS A FILE ~
 
                                                         *lsp-config-merge*
 When an LSP client starts, it resolves its configuration by merging the
-following sources (merge semantics defined by |vim.tbl_deep_extend()|), in
-order of increasing priority:
+following sources (merge semantics defined by |vim.tbl_deep_extend()| with
+"force" behavior), in order of increasing priority:
 
 1. Configuration defined for the `'*'` name.
 2. Configuration from the result of merging all tables returned by