aboutsummaryrefslogtreecommitdiff
path: root/test/functional/vimscript/executable_spec.lua
diff options
context:
space:
mode:
authorMathias Fußenegger <mfussenegger@users.noreply.github.com>2026-02-25 19:26:56 +0100
committerGitHub <noreply@github.com>2026-02-25 13:26:56 -0500
commit583308f5991c4c55d3f04e456254d95433033c72 (patch)
tree88ea1d48732693f1c3590a78a79e672a9b40119e /test/functional/vimscript/executable_spec.lua
parent4ef217e272c463896b73ba726b0a498c497413a0 (diff)
downloadrneovim-583308f5991c4c55d3f04e456254d95433033c72.tar.gz
rneovim-583308f5991c4c55d3f04e456254d95433033c72.tar.bz2
rneovim-583308f5991c4c55d3f04e456254d95433033c72.zip
fix(diagnostic): handle stale diagnostic extmark ids #38060
Problem: If a server is slow with catching up, there can be stale diagnostics for deleted lines. Then if a user uses `jump` it can error like: E5108: Lua: ...runtime/lua/vim/diagnostic.lua:670: attempt to index a nil value stack traceback: ...runtime/lua/vim/diagnostic.lua:670: in function 'get_logical_pos' ...runtime/lua/vim/diagnostic.lua:687: in function 'diagnostic_lines' ...runtime/lua/vim/diagnostic.lua:1122: in function 'next_diagnostic' ...runtime/lua/vim/diagnostic.lua:1665: in function 'jump' Solution: Fallback to diagnostic location. That's better than the failure.
Diffstat (limited to 'test/functional/vimscript/executable_spec.lua')
0 files changed, 0 insertions, 0 deletions