diff options
| -rw-r--r-- | runtime/doc/lsp.txt | 6 | ||||
| -rw-r--r-- | runtime/lua/vim/lsp.lua | 5 |
2 files changed, 2 insertions, 9 deletions
diff --git a/runtime/doc/lsp.txt b/runtime/doc/lsp.txt index 56d7b98a3c..54a8854334 100644 --- 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 index 8608bdfa57..689d942d72 100644 --- 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. |