neovim/runtime/lua/vim/lsp/util.lua, branch dependabot/github_actions/github-actions-c6747d2992

fix(lsp): malformed edit if apply_text_edits() is called twice #34954

2026-04-23T16:01:44Z

Problem: Use vim.lsp.util.apply_text_edits to re-apply the same textedit causes an incorrect edit, because apply_text_edits silently modifies the parameter. Solution: - Avoid changing `text_edit._index`. - Document this fun feature. Helped-by: Riley Bruins Helped-by: Yi Ming Co-authored-by: Justin M. Keyes

fix(lsp): set 'winfixbuf' in open_floating_preview() window #39058

2026-04-15T21:14:35Z

Problem: The window opened by `vim.lsp.util.open_floating_preview()` allows its buffer to be switched. Presumably that only happens by accident and is disorienting. Solution: Set 'winfixbuf' in the open_floating_preview() window.

refactor(api): rename "window" to "win" (positional parameters) #39083

2026-04-15T17:31:17Z

continues d0af4cd9094f. This commit renames positional parameters. This is only "cosmetic", but is intended to make it extra clear which name is preferred, since people often copy existing code despite the guidelines in `:help dev-naming`.

docs: lsp, options, api #38980

2026-04-14T10:09:54Z

docs: lsp, options - revert bogus change to `_meta/builtin_types.lua` from 3a4a66017b74 Close #38991 Co-authored-by: David Mejorado

fix(lsp): show_document can't position cursor past EOL in insert-mode #38566

2026-04-12T15:46:24Z

Problem: vim.lsp.util.show_document insert mode is unable to set the cursor after the target character position if the target character is at end of line. Solution: Move cursor after the target character (in append position) in this case.

feat(api): rename buffer to buf #35330

2026-04-09T00:34:47Z

Problem: `:help dev-name-common` states that "buf" should be used instead of "buffer" but there are cases where buffer is mentioned in the lua API. Solution: - Rename occurrences of "buffer" to "buf" for consistency with the documentation. - Support (but deprecate) "buffer" for backwards compatibility. Co-authored-by: Justin M. Keyes

fix(lsp): apply_text_edits causes unwanted BufDelete events #38778

2026-04-08T21:10:52Z

Problem: Since 2f6d1d3c887a87d9402137425b418dd12a904aac, `apply_text_edits` unconditionally sets `buflisted=true`, causing spurious BufDelete events if plugins restore the original 'buflisted' state on unlisted buffers: https://github.com/neovim/neovim/blob/65ef6cec1cb766334c59d3255595dfe523b11020/src/nvim/option.c#L2159-L2169 Solution: - Don't set 'buflisted' in `apply_text_edits`. Set it more narrowly, in `apply_workspace_edit` where the semantics requires affected buffers to be visible to the user. - Also skip setting 'buflisted' if it would not be changed, to avoid redundant `OptionSet` events.

refactor: integer functions, optimize asserts #34112

2026-03-12T15:04:05Z

refactor(lua): add integer coercion helpers Add vim._tointeger() and vim._ensure_integer(), including optional base support, and switch integer-only tonumber()/assert call sites in the Lua runtime to use them. This also cleans up related integer parsing in LSP, health, loader, URI, tohtml, and Treesitter code. supported by AI

fix(lsp): set concealcursor='' in LSP floating windows #36596

2025-11-18T01:49:14Z

Problem: Users often jump and navigate through LSP windows to yank text. Concealed markdown can make navigation through hyperlinks and code blocks more difficult. Solution: Change 'concealcursor' from 'n' to '' to preserve clean display while improving navigation and selection of the LSP response. Closes #36537

fix(lsp): set 'linebreak' in floating windows (#36275)

2025-10-22T17:38:47Z

Set linebreak to avoid splitting words. Fix #36268