aboutsummaryrefslogtreecommitdiff
path: root/test/functional/vimscript/executable_spec.lua
diff options
context:
space:
mode:
authorAaron Tinio <aptinio@gmail.com>2026-06-11 07:25:13 +0800
committerGitHub <noreply@github.com>2026-06-10 23:25:13 +0000
commitd42f7ee9dcbbece1c65d901fb9825fbe97eeedce (patch)
tree6c3ff90b679c18614569ad527b21cdf07a860e2d /test/functional/vimscript/executable_spec.lua
parent16549f2f40379342c37650be216ed5fe36f562e6 (diff)
downloadrneovim-d42f7ee9dcbbece1c65d901fb9825fbe97eeedce.tar.gz
rneovim-d42f7ee9dcbbece1c65d901fb9825fbe97eeedce.tar.bz2
rneovim-d42f7ee9dcbbece1c65d901fb9825fbe97eeedce.zip
fix(lsp): trailing blank line when edit inserts past end of buffer #40133
Problem: A text edit positioned entirely past the last buffer line, with newText ending in a newline, leaves a stray blank line: the past-the-end path appends the trailing empty fragment produced by vim.split() and does not set has_eol_text_edit, so the end-of-buffer cleanup is skipped. Formatting servers emit such edits whenever formatting moves text to the end of a document. Regression from ec94014cd1 (#20137), which split the past-the-end fast path off the clamp path that sets the flag. Solution: Set has_eol_text_edit in the past-the-end path, like the adjacent path that clamps end_row.
Diffstat (limited to 'test/functional/vimscript/executable_spec.lua')
0 files changed, 0 insertions, 0 deletions