summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMagnus Groß <21310755+vimpostor@users.noreply.github.com>2022-08-23 13:22:14 +0200
committerGitHub <noreply@github.com>2022-08-23 20:22:14 +0900
commitd93bc2baf7532818e83bf2fac61fcd591beb6151 (patch)
tree79b9b98beb12016b08e66ae911b2a412162144f5 /doc
parent992476982ab97bfa7298f5da1ec0d38026f5960a (diff)
downloadale-d93bc2baf7532818e83bf2fac61fcd591beb6151.zip
Use native virtual-text for vim9 (#4281)
Our current virtual text implementation for vim emulates it by abusing the textprop and popupwin feature from vim 8.2 (for more details see commit 708e810414d124b17b0c42e872b387a7a6c2ea85). This implementation sometimes is janky, for example the popups may leak into other vim windows next to the current window. Luckily, vim just got native virtual-text support as a proper subtype to the prop_add() function. By using the 'text' option, the text property automatically becomes virtual text that is appended to the current line if col is zero. Note that the prop_add() method now returns negative IDs for virtual text properties. This feature was added in vim 9.0.0067, but it got a lot of bugfixes which is why we only use this new API if vim has at least version 9.0.0214. However, there are still some minor bugs with vim's native virtual text, so we might have to bump the version check again in the future. Also see #3906. Now with proper virtual text support for both vim and neovim available, we can tackle #2962 in the future by simply tracking multiple virt-texts instead of just the last one. In the future we might also want to disable our virtual text emulation support for vim, as it is a total hack, but for now we should keep it for backwards compatibility.
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions