rneovim.git - Neovim fork with Rahm's personal hacks.

	Commit message (Collapse)	Author	Age
*	test: improve test conventions	dundargoc	2024-04-23
\| \| \| \| \| \| \| \| \|	Specifically, functions that are run in the context of the test runner are put in module `test/testutil.lua` while the functions that are run in the context of the test session are put in `test/functional/testnvim.lua`. Closes https://github.com/neovim/neovim/issues/27004.
*	refactor(test): inject after_each differently	Lewis Russell	2024-04-10
\|
*	test: improve test conventions	dundargoc	2024-04-08
\| \| \| \|	Work on https://github.com/neovim/neovim/issues/27004.
*	fix(api): set script context when using nvim_set_hl (#28123)	zeertzjq	2024-03-31
\|
*	fix: explain that user should run nvim with -V1 to see more information	dundargoc	2024-03-30
\| \| \| \| \|	It's not obvious for users how to figure out where a mapping is set from only "Last set from Lua".
*	test: rename (meths, funcs) -> (api, fn)	Lewis Russell	2024-01-12
\|
*	test: typing for helpers.meths	Lewis Russell	2024-01-12
\|
*	refactor: format test/*	Justin M. Keyes	2024-01-03
\|
*	refactor(options): deprecate nvim[_buf\|_win]_[gs]et_option	Lewis Russell	2023-05-21
\| \| \| \| \|	Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: famiu <famiuhaque@protonmail.com>
*	test: use exec_capture() in more places (#22787)	zeertzjq	2023-03-26
\| \| \| \| \| \| \|	Problem: Using `meths.exec2("code", { output = true })` is too verbose. Solution: Use exec_capture() in more places.
*	feat(api): nvim_exec2(), deprecate nvim_exec() #19032	Evgeni Chasnovski	2023-03-25
\| \| \| \| \| \| \|	Problem: The signature of nvim_exec() is not extensible per ":help api-contract". Solution: Introduce nvim_exec2() and deprecate nvim_exec().
*	fix(api): set script context when setting usercmd or option (#22624)	zeertzjq	2023-03-11
\|
*	docs: fix typos	dundargoc	2022-11-02
\|
*	refactor!: rename nvim_add_user_command to nvim_create_user_command	Gregory Anders	2022-04-10
\|
*	fix: anonymous sid not working	shadmansaleh	2022-02-28
\|
*	feat(lua): show proper verbose output for lua configuration	shadmansaleh	2022-02-28
	`:verbose` didn't work properly with lua configs (For example: options or keymaps are set from lua, just say that they were set from lua, doesn't say where they were set at. This fixes that issue. Now `:verbose` will provide filename and line no when option/keymap is set from lua. Changes: - compiles lua/vim/keymap.lua as vim/keymap.lua - When souring a lua file current_sctx.sc_sid is set to SID_LUA - Moved finding scripts SID out of `do_source()` to `get_current_script_id()`. So it can be reused for lua files. - Added new function `nlua_get_sctx` that extracts current lua scripts name and line no with debug library. And creates a sctx for it. NOTE: This function ignores C functions and blacklist which currently contains only vim/_meta.lua so vim.o/opt wrappers aren't targeted. - Added function `nlua_set_sctx` that changes provided sctx to current lua scripts sctx if a lua file is being executed. - Added tests in tests/functional/lua/verbose_spec.lua - add primary support for additional types (:autocmd, :function, :syntax) to lua verbose Note: These can't yet be directly set from lua but once that's possible :verbose should work for them hopefully :D - add :verbose support for nvim_exec & nvim_command within lua Currently auto commands/commands/functions ... can only be defined by nvim_exec/nvim_command this adds support for them. Means if those Are defined within lua with vim.cmd/nvim_exec :verbose will show their location . Though note it'll show the line no on which nvim_exec call was made.