diff options
| author | Phạm Bình An <111893501+brianhuster@users.noreply.github.com> | 2025-07-19 03:02:09 +0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-18 13:02:09 -0700 |
| commit | f2691199fadd132336685f88bac1d3a8c4b9c62d (patch) | |
| tree | d2bf450fd03363ed0ea9eeb15155c9b16fc29014 /runtime/lua/vim/provider/python.lua | |
| parent | 26bbeadda3f1110713c2a766f930686d05eae05b (diff) | |
| download | rneovim-f2691199fadd132336685f88bac1d3a8c4b9c62d.tar.gz rneovim-f2691199fadd132336685f88bac1d3a8c4b9c62d.tar.bz2 rneovim-f2691199fadd132336685f88bac1d3a8c4b9c62d.zip | |
fix(tutor): use invalidate field in nvim_buf_set_extmark() #34989
Problem:
If users delete a line containing extmark, it will move to the next
line, which could highlight the next line in an unwanted way.
Solution:
- Use `invalidate` field in `nvim_buf_set_extmark()` to prevent the
extmark from moving.
- Also save from "priority" hacking, since we can check if the extmark
is valid in `nvim_buf_get_extmarks()` now.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions