neovim - Vim-fork focused on extensibility and usability

Age	Commit message (Collapse)	Author	Files
2026-02-17	test: don't run test cases directly in describe() (#37915)	zeertzjq	1

2025-03-26	fix(lua): no omni/cmdline completion for vim.env (#33044)	Phạm Bình An	1
	Problem: - `:lua vim.env.<Tab>` does not show completion of environment variables - Meanwhile, `:let $<Tab>` does show completion of environment variables Solution: - Fix it
2025-03-24	fix(cmdline): cmdline completion of _defer_require() modules #33007	phanium	1
	Problem: `:lua vim.lsp.c<tab>` does not list vim.lsp.completion in the completion list after 24cea4c7f7417c7fe99a98a0487f51dd68c4f409. Solution: - Always include `vim.lsp._submodule` keys in candidates. - Fixes `vim.lsp.c<tab>` -> `vim.lsp.completion`. - Eager-load `vim.lsp.completion` to get its completion. - Fixes `vim.lsp.completion.g<tab>` -> `vim.lsp.completion.get`.
2025-03-02	docs: misc #31996	Justin M. Keyes	1

2025-03-02	feat(lua): don't complete private (_) fields after dot (.) #32690	Maria José Solano	1

2024-10-04	feat(lua): completion for vim.fn, vim.v, vim.o #30472	Jongwook Choi	1
	Problem: Lua accessors for - global, local, and special variables (`vim.{g,t,w,b,v}.`), and - options (`vim.{o,bo,wo,opt,opt_local,opt_global}.`), do not have command-line completion, unlike their vimscript counterparts (e.g., `g:`, `b:`, `:set`, `:setlocal`, `:call <fn>`, etc.). Completion for vimscript functions (`vim.fn.*`) is incomplete and does not list all the available functions. Solution: Implement completion for vimscript function, variable and option accessors in `vim._expand_pat` through: - `getcompletion()` for variable and vimscript function accessors, and - `nvim_get_all_options_info()` for option accessors. Note/Remark: - Short names for options are yet to be implemented. - Completions for accessors with handles (e.g. `vim.b[0]`, `vim.wo[0]`) are also yet to be implemented, and are left as future work, which involves some refactoring of options. - For performance reasons, we may want to introduce caching for completing options, but this is not considered at this time since the number of the available options is not very big (only ~350) and Lua completion for option accessors appears to be pretty fast. - Can we have a more "general" framework for customizing completions? In the future, we may want to improve the implementation by moving the core logic for generating completion candidates to each accessor (or its metatable) or through some central interface, rather than writing all the accessor-specific completion implementations in a single function: `vim._expand_pat`.
2024-04-23	test: improve test conventions	dundargoc	1
	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.
2024-04-10	refactor(test): inject after_each differently	Lewis Russell	1

2024-04-08	test: improve test conventions	dundargoc	1
	Work on https://github.com/neovim/neovim/issues/27004.
2024-01-03	refactor: format test/*	Justin M. Keyes	1

2023-05-21	refactor(options): deprecate nvim[_buf\|_win]_[gs]et_option	Lewis Russell	1
	Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: famiu <famiuhaque@protonmail.com>
2023-03-06	feat(lua): omnifunc for builting lua interpreter	Björn Linse	1
	also make implicit submodules "uri" and "_inspector" work with completion this is needed for `:lua=vim.uri_<tab>` wildmenu completion to work even before uri or _inspector functions are used.
2022-03-09	feat(lua): handle lazy submodules in `:lua vim.` wildmenu completion	bfredl	1

2021-01-26	lint	chentau	1

2021-01-26	Don't show entire context when completing	Tony Chen	1

2021-01-26	feat: add completion to ':lua'	TJ DeVries	1