diff options
| author | bfredl <bjorn.linse@gmail.com> | 2023-11-03 12:26:38 +0100 |
|---|---|---|
| committer | bfredl <bjorn.linse@gmail.com> | 2023-11-05 12:18:29 +0100 |
| commit | 68cb4a7405ea9f8841d1f25ee8997c49e77fa679 (patch) | |
| tree | f2766eca6c0cb9fefb9739ffc3256649ba8d4a61 /runtime | |
| parent | 92e99bb1058dd837c451675175efb8511c5f8e15 (diff) | |
| download | rneovim-68cb4a7405ea9f8841d1f25ee8997c49e77fa679.tar.gz rneovim-68cb4a7405ea9f8841d1f25ee8997c49e77fa679.tar.bz2 rneovim-68cb4a7405ea9f8841d1f25ee8997c49e77fa679.zip | |
feat(extmarks): add "undo_restore" flag to opt out of undo-restoring
It is a design goal of extmarks that they allow precise tracking
of changes across undo/redo, including restore the exact positions
after a do/undo or undo/redo cycle. However this behavior is not useful
for all usecases. Many plugins won't keep marks around for long after
text changes, but uses them more like a cache until some external source
(like LSP semantic highlights) has fully updated to changed text and
then will explicitly readjust/replace extmarks as needed.
Add a "undo_restore" flag which is true by default (matches existing
behavior) but can be set to false to opt-out of this behavior.
Delete dead u_extmark_set() code.
Diffstat (limited to 'runtime')
| -rw-r--r-- | runtime/doc/news.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/runtime/doc/news.txt b/runtime/doc/news.txt index b88b7d164f..e32e1aadb6 100644 --- a/runtime/doc/news.txt +++ b/runtime/doc/news.txt @@ -270,6 +270,9 @@ The following changes to existing APIs or features add new behavior. In addition, |nvim_buf_get_extmarks()| has gained an "overlap" option to return such ranges even if they started before the specified position. +• Extmarks can opt-out of precise undo tracking using the new "undo_restore" + flag to |nvim_buf_set_extmark()| + • LSP hover and signature help now use Treesitter for highlighting of Markdown content. Note that syntax highlighting of code examples requires a matching parser |