| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | docs: misc #31996 | Justin M. Keyes | 2025-03-02 |
| | | |||
| * | feat(lua): don't complete private (_) fields after dot (.) #32690 | Maria José Solano | 2025-03-02 |
| | | |||
| * | feat(lua): completion for vim.fn, vim.v, vim.o #30472 | Jongwook Choi | 2024-10-04 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`. | ||
| * | 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. | ||
| * | 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> | ||
| * | feat(lua): omnifunc for builting lua interpreter | Björn Linse | 2023-03-06 |
| | | | | | | | | 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. | ||
| * | feat(lua): handle lazy submodules in `:lua vim.` wildmenu completion | bfredl | 2022-03-09 |
| | | |||
| * | lint | chentau | 2021-01-26 |
| | | |||
| * | Don't show entire context when completing | Tony Chen | 2021-01-26 |
| | | |||
| * | feat: add completion to ':lua' | TJ DeVries | 2021-01-26 |
 |
index : rneovim.git | |
| Neovim fork with Rahm's personal hacks. |
| aboutsummaryrefslogtreecommitdiff |