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
tests	Make m textobject look for pairs enclosing selections (#3344)	2023-02-10 13:52:57 -06:00
.gitignore	Initial import.	2020-05-20 18:14:51 +09:00
build.rs	feat(lsp): pass client_info on initialization (#4904)	2022-12-08 21:57:03 -06:00
Cargo.toml	build(deps): bump indoc from 1.0.8 to 2.0.0 (#5742)	2023-01-30 17:47:30 -06:00