rneovim.git/test/functional/plugin/lsp/incremental_sync_spec.lua, branch fix_repeatcmdline Neovim fork with Rahm's personal hacks. test: don't unnecessarily specify win/buf for `nvim_(get|set)_option_value` 2023-05-22T07:02:07+00:00 Famiu Haque famiuhaque@proton.me 2023-05-22T06:47:10+00:00 576dddb46168e81aa0f78c28816082c662dedea1 `nvim_(get|set)_option_value` pick the current buffer / window by default for buffer-local/window-local (but not global-local) options. So specifying `buf = 0` or `win = 0` in opts is unnecessary for those options. This PR removes those to reduce code clutter. 
`nvim_(get|set)_option_value` pick the current buffer / window by default for buffer-local/window-local (but not global-local) options. So specifying `buf = 0` or `win = 0` in opts is unnecessary for those options. This PR removes those to reduce code clutter.
refactor(options): deprecate nvim[_buf|_win]_[gs]et_option 2023-05-21T09:14:01+00:00 Lewis Russell lewis6991@gmail.com 2022-12-19T16:37:45+00:00 1fe1bb084d0099fc4f9bfdc11189485d0f74b75a Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: famiu <famiuhaque@protonmail.com> 
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
Co-authored-by: famiu <famiuhaque@protonmail.com>
fix(lsp): handle insertion of previous line (#17618) 2022-03-06T15:52:11+00:00 Michael Lingelbach m.j.lbach@gmail.com 2022-03-06T15:52:11+00:00 3800615da9eaf9e8b26d9040c882c74084d688e4 






fix(lsp): start incremental sync range at previous newline character (#17610)
2022-03-05T17:17:56+00:00

Michael Lingelbach
m.j.lbach@gmail.com

2022-03-05T17:17:56+00:00

a5e475fcc269b32a8a487f787af20802cbfabe28

This change forces the start of an incremental sync range to begin always on an existing line.




This change forces the start of an incremental sync range to begin always on an existing line.






fix(lsp): correctly align start and end range to codepoints during incremental sync (#16670)
2021-12-18T02:05:00+00:00

Rishikesh Vaishnav
rishhvaishnav@gmail.com

2021-12-18T02:05:00+00:00

36c401db243da08a60bde7f2c42e1ed9f5204c85

Closes #16624

Fixes two issues with aligning the start position and end position to
codepoints when calculating the start and end range.

When aligning the start position:
* use aligned byte index to calculate character index rather than 
  the unadjusted byte

When aligning the end position:
* do not adjust the end byte if it falls on a UTF-8 codepoint
* align byte to the first byte of the next codepoint rather than the
  last byte of the current codepoint
* compute character character end range on the aligned byte index

This commit also adds additional test coverage, including multibyte operations
that previously failed before this commit.




Closes #16624

Fixes two issues with aligning the start position and end position to
codepoints when calculating the start and end range.

When aligning the start position:
* use aligned byte index to calculate character index rather than 
  the unadjusted byte

When aligning the end position:
* do not adjust the end byte if it falls on a UTF-8 codepoint
* align byte to the first byte of the next codepoint rather than the
  last byte of the current codepoint
* compute character character end range on the aligned byte index

This commit also adds additional test coverage, including multibyte operations
that previously failed before this commit.






fix(lsp): improve incremental sync robustness (#16358)
2021-11-18T21:49:46+00:00

Michael Lingelbach
m.j.lbach@gmail.com

2021-11-18T21:49:46+00:00

f71be1f87b40bf863b6cf6b4fbcebffdd3297d88

closes https://github.com/neovim/neovim/issues/16352

* improve handling of multi-byte deletions




closes https://github.com/neovim/neovim/issues/16352

* improve handling of multi-byte deletions






fix(lsp): fix edge cases in incremental sync (#16308)
2021-11-15T16:51:30+00:00

Michael Lingelbach
m.j.lbach@gmail.com

2021-11-15T16:51:30+00:00

87a053f126c79f5eeb1654e35beb31d9fe733163












fix(lsp): rewrite incremental sync (#16252)
2021-11-09T22:37:48+00:00

Michael Lingelbach
m.j.lbach@gmail.com

2021-11-09T22:37:48+00:00

2ecf0a4c6183bba1c65d440711038f040d355fef

* use codeunits/points instead of byte ranges when applicable
* take into account different file formats when computing range and
  sending text (dos, unix, and mac supported)
* add tests of incremental sync




* use codeunits/points instead of byte ranges when applicable
* take into account different file formats when computing range and
  sending text (dos, unix, and mac supported)
* add tests of incremental sync