Pascal Kuthe 93c7afc4ed Negotiate LSP Position Encoding (#5894) ... So far LSP always required that `PositionEncoding.characters` is an UTF-16 offset. Now that LSP 3.17 is available in `lsp-types` request the server to send char offsets (UTF-32) or byte offsets (UTF-8) instead. For compatability with old servers, UTF-16 remains as the fallback as required by the standard.		2023-02-11 15:50:01 +09:00
..
src	Negotiate LSP Position Encoding (#5894)	2023-02-11 15:50:01 +09:00
Cargo.toml	Negotiate LSP Position Encoding (#5894)	2023-02-11 15:50:01 +09:00