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

fix(path): normalize path slashes on Windows #37729

2026-04-24T17:20:25Z

Problem: On Windows, path separators may become inconsistent for various reasons, which makes normalization quite painful. Solution: Normalize paths to `/` at the entry boundaries and always use it internally, converting back only in rare cases where `\` is really needed (e.g. cmd.exe/bat scripts?). This is the first commit in a series of incremental steps. Note: * some funcs won't respect shellslash. e.g. `expand/fnamemodify` * some funcs still respect shellslash, but will be updated in a follow PR. e.g. `ex_pwd/f_chdir/f_getcwd` * uv's built-in funcs always return `\`. e.g. `uv.cwd/uv.exepath` Co-authored-by: Justin M. Keyes

refactor(test): drop deprecated exc_exec #39242

2026-04-20T18:16:41Z

fix(terminal): forward streamed bracketed paste properly (#39152)

2026-04-17T22:33:52Z

feat(api): rename buffer to buf in retval #38900

2026-04-13T16:42:26Z

In 3a4a66017b74192caaf9af9af172bdc08e0c1608, 4d3a67cd620152d11ab9b5f5bdd973f84cc2d44b we renamed "buffer" to "buf" in dict parameters. This commit also renames such keys in dict return-values.

fix(api): avoid error when parsing invalid expr after :echo (#38695)

2026-04-01T23:05:47Z

Problem: Parsing :echo followed by invalid expression leads to error. Solution: Suppress error when skipping over expression.

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.

fix(api): nvim_get_option_value FileType autocmd handling #37414

2026-03-19T00:11:59Z

Problem: nvim_get_option_value with "filetype" set silently returns incorrect defaults if autocommands are blocked, like when they're already running. Solution: Allow its FileType autocommands to nest: `do_filetype_autocmd(force=true)`. Also error if executing them fails, rather than silently return wrong defaults. Endless nesting from misbehaving scripts should be prevented by the recursion limit in apply_autocmds_group, which is 10.

fix(api): use standard error messages

2026-03-16T13:52:04Z

fix(messages): allocate message history kind string #38292

2026-03-14T12:07:55Z

Problem: nvim_echo()->kind memory may be used after it is freed with :messages. Solution: Copy and free message kind string in message history.

docs: misc

2026-03-13T19:32:01Z