wyj/neovim
1
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-09-17 20:58:20 -04:00
Code Issues Packages Projects Releases Wiki Activity

fix(lsp): use only utf-16 in default client positionEncodings (#23903)

Browse Source 
The Nvim client does not yet support multiple offset encodings for
clients in the same buffer. Until it does, stick to utf-16 by default.
This commit is contained in:
Gregory Anders 2023-06-05 08:21:23 -05:00 committed by GitHub
parent 21187e1c73
commit ca26ec3438
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
runtime/doc/news.txt
View File

@ -44,11 +44,9 @@ The following new APIs or features were added.
• Neovim's LSP client now always saves and restores named buffer marks when
applying text edits.
• 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.
• Nvim now supports the `positionEncoding` server capability. If a 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

2
runtime/lua/vim/lsp/protocol.lua
View File

@ -636,9 +636,7 @@ function protocol.make_client_capabilities()
return {
general = {
positionEncodings = {
'utf-8',
'utf-16',
'utf-32',
},
},
textDocument = {