neovim/test/functional/lua/vim_spec.lua, branch master

perf(vim.fn): call Lua-implemented vim.fn.xx() directly #39166

2026-04-17T23:10:20Z

Problem: - Builtin "Vimscript" functions (f_xx) are mostly implemented in C. Partly that's because there is some boilerplate required to call out to Lua. - Calls to `vim.fn.foo()` always marshall over the Lua <=> Vimscript ("typval") bridge, even if `fn.foo()` is implemented entirely in Lua: ``` Lua => typval => Object => Lua => Object => typval => Lua. ``` Solution: Functions declared in eval.lua with `func_lua` are implemented in entirely in Lua (`_core/vimfn.lua`). - `gen_eval.lua` wires `func_lua` entries to `lua_wrapper`, which handles the typval conversion for Vimscript callers (slow path). - `nlua_call()` detects `func_lua` functions and calls the Lua implementation directly. This eliminates all conversion overhead for Lua callers (fast path). - Validate at build-time that `func`, `func_float`, and `func_lua` are mutually exclusive. - Migrate `hostname()` as a toy example, to show the idea.

test: replace busted with local harness

2026-04-15T11:09:25Z

Replace the busted-based Lua test runner with a repo-local harness. The new harness runs spec files directly under `nvim -ll`, ships its own reporter and lightweight `luassert` shim, and keeps the helper/preload flow used by the functional and unit test suites. Keep the file boundary model shallow and busted-like by restoring `_G`, `package.loaded`, `package.preload`, `arg`, and the process environment between files, without carrying extra reset APIs or custom assertion machinery. Update the build and test entrypoints to use the new runner, add black-box coverage for the harness itself, and drop the bundled busted/luacheck dependency path. AI-assisted: Codex

fix(lua): make vim.deep_equal cycle-safe

2026-04-15T08:26:45Z

AI-assisted: Codex

fix(messages): truncate warning messages only in display (#38901)

2026-04-09T04:11:32Z

For now, add a private "_truncate" flag to nvim_echo, using a truncation method similar to showmode().

fix(lua): drop support for boolean `buf` in `vim.keymap` #38432

2026-03-23T12:00:53Z

Problem: `vim.keymap.*.Opts.buf` allows `boolean` aliases for more widely used `integer?` values, `true` -> `0` and `false` -> `nil`. This conversion is unnecessary and can be handled at call sites. Solution: As a follow-up to deprecating the `buffer` option, drop support for boolean values for the new `buf` option. The deprecated `buffer` continues to support booleans for backward compatibility.

feat(lua): replace `buffer` with `buf` in vim.keymap.set/del #38360

2026-03-21T16:00:06Z

The `buffer` option remains functional but is now undocumented. Providing both will raise an error. Since providing `buf` was disallowed before, there is no code that will break due to using `buffer` alongside `buf`.

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.

build: move shared.lua to _core/

2025-12-30T06:44:52Z

docs(lua): iInconsistent vim.keymap param name #37026

2025-12-21T00:26:44Z

Problem: vim.keymap.del has 'modes' as it's first argument while vim.keymap.set has 'mode' as it's first argument despite both 'mode' and 'modes' taking in the same type input of String or String[]. Solution: Updated vim.keymap.set docs to refer to it's first argument as 'modes'.