aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/_ftplugin/lua.lua
diff options
context:
space:
mode:
authorRiley Bruins <ribru17@hotmail.com>2025-11-09 17:49:25 -0800
committerGitHub <noreply@github.com>2025-11-09 17:49:25 -0800
commitc2c5a0297e0048a7d1b75e03e1ae7d4229052108 (patch)
treeefb9bd2e1a143889adbb86313aa036ba4c743804 /runtime/lua/vim/_ftplugin/lua.lua
parentc6dad6e9dffec12556355a1a50cf4e74aaee7e81 (diff)
downloadrneovim-c2c5a0297e0048a7d1b75e03e1ae7d4229052108.tar.gz
rneovim-c2c5a0297e0048a7d1b75e03e1ae7d4229052108.tar.bz2
rneovim-c2c5a0297e0048a7d1b75e03e1ae7d4229052108.zip
fix(lsp): don't overlay insertion-style inline completions (#36477)
* feat(lua): `Range:is_empty()` to check vim.range emptiness * fix(lsp): don't overlay insertion-style inline completions **Problem:** Some servers commonly respond with an empty inline completion range which acts as a position where text should be inserted. However, the inline completion module assumes that all responses with a range are deletions + insertions that thus require an `overlay` display style. This causes an incorrect preview, because the virtual text should have the `inline` display style (to reflect that this is purely an insertion). **Solution:** Only use `overlay` for non-empty replacement ranges.
Diffstat (limited to 'runtime/lua/vim/_ftplugin/lua.lua')
0 files changed, 0 insertions, 0 deletions