neovim/src/nvim/lua/executor.c, branch release-0.12

fix(lua): don't strip debuginfo in precompile module #39191

2026-04-23T17:06:31Z

Problem: debug.getinfo on bytecode module/func don't give you detail source info. Solution: - Use `loadstring`+`string.dump` to replace LUAC_PRG(`luac`/`luajit -b`) - `string.dump(…,false)` to generate non-strip version bytecode - `loadstring(…,fname)` to specify the full source name BEFORE: $ nvim --clean +'=debug.getinfo(vim.fn.maparg("]", "n", 0, 1).callback, "Sl")' --headless +q { currentline = -1, lastlinedefined = 456, linedefined = 452, short_src = "?", source = "=?", what = "Lua" } AFTER: $ nvim --clean +'=debug.getinfo(vim.fn.maparg("]", "n", 0, 1).callback, "Sl")' --headless +q { currentline = -1, lastlinedefined = 456, linedefined = 452, short_src = "/home/xx/b/neovim/runtime/lua/vim/_core/defaults.lua", source = "@/home/xx/b/neovim/runtime/lua/vim/_core/defaults.lua", what = "Lua" } (cherry picked from commit 398f2c108d8ee3ce7ac950b60520a9569b63da67)

feat(eval): treat Lua string as "blob" in writefile() #39098

2026-04-22T17:56:29Z

Problem: vim.fn.writefile() treats Lua strings as Vimscript strings instead of a "binary clean" string. Solution: Treat Lua-originated strings as blob data. (cherry picked from commit fb6aeaba2d3a38c7febd0a39cabd89685de11b9d)

docs: news #38464

2026-03-28T13:59:54Z

fix(messages): disallow user-defined integer message-id #38359

2026-03-19T01:07:17Z

Problem: `nvim_echo(…, {id=…})` accepts user-defined id as a string or integer. Generated ids are always higher than last highest msg-id used. Thus plugins may accidentally advance the integer id "address space", which, at minimum, could lead to confusion when troubleshooting, or in the worst case, could overflow or "exhaust" the id address space. There's no use-case for it, and it could be the mildly confusing, so we should just disallow it. Solution: Disallow *integer* user-defined message-id. Only allow *string* user-defined message-id.

docs: api, messages, lsp, trust

2026-03-11T17:00:18Z

gen_vimdoc.lua: In prepare for the upcoming release, comment-out the "Experimental" warning for prerelease features.

fix(cmdline): cmdline_block events for :lua debug.debug() #38171

2026-03-06T18:17:12Z

Problem: :lua debug.debug() is missing cmdline_block events. Solution: Emit cmdline_block_show/append/hide events for :lua debug.debug().

fix: wait() checks condition twice on each interval (#37837)

2026-02-13T13:02:40Z

Problem: wait() checks condition twice on each interval. Solution: Don't schedule the due callback. Also fix memory leak when Nvim exits while waiting. No test that the condition isn't checked twice, as testing for that can be flaky when there are libuv events from other sources.

fix(lua): close vim.defer_fn() timer if vim.schedule() failed (#37647)

2026-02-01T13:29:19Z

Problem: Using vim.defer_fn() just before Nvim exit leaks luv handles. Solution: Make vim.schedule() return an error message if scheduling failed. Make vim.defer_fn() close timer if vim.schedule() failed.

fix(ui): textlock still causes issues for UI callbacks #37513

2026-01-27T14:30:37Z

Problem: There are still ways to run into textlock errors with vim.ui_attach callbacks trying to display a UI event. Solution: Disregard textlock again during vim.ui_attach() callbacks (also when scheduled). Partially revert 3277dc3b; avoiding to flush while textlock is set is still helpful.

fix(lua): correct line number reporting for options set in coroutines (#37463)

2026-01-21T02:18:33Z