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

refactor(test): drop deprecated exc_exec #39242

2026-04-20T18:16:41Z

docs: lsp, misc

2025-09-04T03:03:51Z

- Problem: It's not clear for new plugin developers that `:help` uses a help-tags file for searching the docs, generated by `:helptags`. - Solution: Hint to the |:helptags| docs for regenerating the tags file for their freshly written documentation. Co-authored-by: Yochem van Rosmalen

fix(lua): report error in Lua Funcref callback properly (#35555)

2025-08-30T22:44:23Z

refactor(tests): lint decorations_spec, float_spec, multigrid_spec #33274

2025-05-07T01:00:20Z

Problem: decorations_spec.lua, float_spec.lua, multigrid_spec.lua are not auto-formatted. Solution: Add a special `formatlua2` cmake target, which invokes `stylua` with an alternative `.stylua2.toml` config.

feat(messages): cleanup Lua error messages

2025-05-04T15:22:57Z

"Error" in error messages is redundant. Just provide the context, don't say "Error ...".

fix(tests): needing two calls to setup a screen is cringe

2024-11-14T11:40:57Z

Before calling "attach" a screen object is just a dummy container for (row, col) values whose purpose is to be sent as part of the "attach" function call anyway. Just create the screen in an attached state directly. Keep the complete (row, col, options) config together. It is still completely valid to later detach and re-attach as needed, including to another session.

refactor(api)!: rename Dictionary => Dict

2024-09-23T12:42:57Z

In the api_info() output: :new|put =map(filter(api_info().functions, '!has_key(v:val,''deprecated_since'')'), 'v:val') ... {'return_type': 'ArrayOf(Integer, 2)', 'name': 'nvim_win_get_position', 'method': v:true, 'parameters': [['Window', 'window']], 'since': 1} The `ArrayOf(Integer, 2)` return type didn't break clients when we added it, which is evidence that clients don't use the `return_type` field, thus renaming Dictionary => Dict in api_info() is not (in practice) a breaking change.

refactor(tests): again yet more global highlight definitions

2024-08-14T12:03:34Z

fix(eval): handle wrong v:lua in expr option properly (#29953)

2024-08-02T08:00:27Z

refactor(typval)!: remove distinction of binary and nonbinary strings

2024-06-27T09:04:04Z

This is a breaking change which will make refactor of typval and shada code a lot easier. In particular, code that would use or check for v:msgpack_types.binary in the wild would be broken. This appears to be rarely used in existing plugins. Also some cases where v:msgpack_type.string would be used to represent a binary string of "string" type, we use a BLOB instead, which is vimscripts native type for binary blobs, and already was used for BIN formats when necessary. msgpackdump(msgpackparse(data)) no longer preserves the distinction of BIN and STR strings. This is very common behavior for language-specific msgpack bindings. Nvim uses msgpack as a tool to serialize its data. Nvim is not a tool to bit-perfectly manipulate arbitrary msgpack data out in the wild. The changed tests should indicate how behavior changes in various edge cases.