neovim

commit 15641f38cf4b489a7c83e2c3aa6efc4c63009f00
parent fb54e6980ea6fec218a11f118e97ef65f250395a
Author: Gregory Anders <greg@gpanders.com>
Date:   Thu,  1 Jun 2023 11:39:51 -0500

feat(lsp): include positionEncodings in default client capabilities

Diffstat:
M
runtime/doc/news.txt
 | 
6
++++++
M
runtime/lua/vim/lsp/protocol.lua
 | 
7
+++++++

2 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/runtime/doc/news.txt b/runtime/doc/news.txt
@@ -39,6 +39,12 @@ ADDED FEATURES                                                     *news-added*
 
 The following new APIs or features were added.
 
+• Nvim's LSP client now advertises the general.positionEncodings client
+  capability to indicate to servers that it supports utf-8, utf-16, and utf-32
+  encodings. If the server responds with the positionEncoding capability in
+  its initialization response, Nvim automatically sets the client's
+  `offset_encoding` field.
+
 • Dynamic registration of LSP capabilities. An implication of this change is that checking a client's `server_capabilities` is no longer a sufficient indicator to see if a server supports a feature. Instead use `client.supports_method(<method>)`. It considers both the dynamic capabilities and static `server_capabilities`.
 • |vim.iter()| provides a generic iterator interface for tables and Lua
   iterators |luaref-in|.
diff --git a/runtime/lua/vim/lsp/protocol.lua b/runtime/lua/vim/lsp/protocol.lua
@@ -634,6 +634,13 @@ export interface WorkspaceClientCapabilities {
 --- capabilities.
 function protocol.make_client_capabilities()
   return {
+    general = {
+      positionEncodings = {
+        'utf-8',
+        'utf-16',
+        'utf-32',
+      },
+    },
     textDocument = {
       semanticTokens = {
         dynamicRegistration = false,