commit 15f7ac6a045aad3355e4c6006423fde81644886a
parent 99288ecc77e429ffe06842157e72ed612e97a419
Author: Tim Pope <code@tpope.net>
Date: Sat, 24 Feb 2024 01:19:33 -0500
docs(lsp): remove obsolete didChangeConfiguration explanation (#27595)
Rendered obsolete by c6d747e6a5227e17556c62e16ed054398eb1a89a.
Diffstat:
2 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/runtime/doc/lsp.txt b/runtime/doc/lsp.txt
@@ -1034,11 +1034,7 @@ start_client({config}) *vim.lsp.start_client()*
example, clangd sends `initialize_result.offsetEncoding`
if `capabilities.offsetEncoding` was sent to it. You can
only modify the `client.offset_encoding` here before any
- notifications are sent. Most language servers expect to be
- sent client specified settings after initialization. Nvim
- does not make this assumption. A
- `workspace/didChangeConfiguration` notification should be
- sent to the server during on_init.
+ notifications are sent.
• on_exit Callback (code, signal, client_id) invoked on
client exit.
• code: exit code of the process
diff --git a/runtime/lua/vim/lsp.lua b/runtime/lua/vim/lsp.lua
@@ -641,10 +641,7 @@ end
--- the server may send. For example, clangd sends
--- `initialize_result.offsetEncoding` if `capabilities.offsetEncoding` was
--- sent to it. You can only modify the `client.offset_encoding` here before
---- any notifications are sent. Most language servers expect to be sent client specified settings after
---- initialization. Nvim does not make this assumption. A
---- `workspace/didChangeConfiguration` notification should be sent
---- to the server during on_init.
+--- any notifications are sent.
---
--- - on_exit Callback (code, signal, client_id) invoked on client
--- exit.