aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim
Commit message (Collapse)AuthorAge
...
* fix(lsp): support v:count in selection_range() #34551Riley Bruins2025-06-17
| | | Co-authored-by: Yi Ming <ofseed@foxmail.com>
* docs: vim.fs.dir.Opts type #34546phanium2025-06-17
| | | Follow the pattern of vim.fs.find.Opts
* fix(docs): callback annotation for `vim.ui.input` #34507Maria José Solano2025-06-17
|
* fix(lsp): include client ID when receiving unknown fold kind (#34535)Maria José Solano2025-06-16
|
* fix(lsp): advertise supported fold kinds (#34461)Riley Bruins2025-06-16
| | | | This commit also makes it so that folds which have an unsupported fold kind have their `kind` ignored.
* feat(lsp): handle disabled code actions (#34453)Riley Bruins2025-06-16
| | | | This commit also makes it so that disabled code actions are not displayed unless the trigger kind is "Invoked".
* fix(lsp): add missing argument validations (#34519)Maria José Solano2025-06-16
|
* fix(lsp): use vim.notify for all message types #34489someoneinjd2025-06-16
| | | | | | Problem: Currently, vim.notify is only used to display messages when the message type is Error. Solution: Use vim.notify to display messages for all message types.
* vim-patch:631a50c: runtime(doc): mention cannot ignored events in ↵zeertzjq2025-06-16
| | | | | | | | | eventignorewin (#34522) closes: vim/vim#17545 https://github.com/vim/vim/commit/631a50ceb9a312a9042a8e8420afd8e948497d90 Co-authored-by: glepnir <glephunter@gmail.com>
* docs(meta): fix incorrect bar -> backtick replacement (#34520)zeertzjq2025-06-16
|
* fix(lsp): use correct deprecation function (#34518)Maria José Solano2025-06-15
|
* fix(messages): add append parameter to history entries (#34467)luukvbaal2025-06-15
| | | | | | | | Problem: The "append" parameter added in abb40ece is missing from history entries, resulting in different message formatting for "g<". Solution: Add "append" field to message history entries. Co-authored-by: phanium <91544758+phanen@users.noreply.github.com>
* fix(extui): clear cmdline buffer for first message (#34490)luukvbaal2025-06-15
| | | | | | | | | | | | | | | | | Problem: Cmdline buffer is not cleared for a new message (since c973c7ae), resulting in an incorrect spill indicator. When the cmdline buffer is cleared, "msg_row" is not invalidated, resulting in an error. The extui module is untested. Return value of `vim.ui_attach()->callback` is undocumented. Solution: Clear the cmdline buffer for the first message in an event loop iteration. Ensure msg_row passed as end_row does not exceed buffer length. Add `messages_spec2.lua` to test the extui module, keeping in mind that test coverage will greatly increase if this UI is made the default. As such, only tests for specific extui functionality unlikely to be covered by tests leveraging the current message grid. Document the return value of `vim.ui_attach()->callback`, it seems to make sense, and is also used to suppress remote UI events in `messages_spec2.lua`.
* docs: miscdundargoc2025-06-14
| | | | | | | Co-authored-by: Jan Weinkauff <jan@weinkauff.cloud> Co-authored-by: MeanderingProgrammer <meanderingprogrammer@gmail.com> Co-authored-by: Yochem van Rosmalen <git@yochem.nl> Co-authored-by: phanium <91544758+phanen@users.noreply.github.com>
* feat(lsp): support multiline semantic tokens #34458Riley Bruins2025-06-13
|
* docs: vim.fs., diagnostics, lsp #34402Justin M. Keyes2025-06-13
|
* feat(treesitter)!: apply `offset!` directive to all captures #34383Riley Bruins2025-06-13
| | | | | | | | | | | | | | | | | This commit changes the `offset!` directive so that instead of setting a `metadata.range` value for the entire pattern, it will set a `metadata.offset` value. This offset will be applied to the range only in `vim.treesitter.get_range()`, rather than at directive application time. This allows the offset to be applied to any and all nodes captured by the given pattern, and removes the requirement that `#offset!` be applied to only a single node. The downside of this change is that plugins which read from `metadata.range` may be thrown off course, but such plugins should prefer `vim.treesitter.get_range()` when retrieving ranges anyway. Note that `#trim!` still sets `metadata.range`, and `vim.treesitter.get_range()` still reads from `metadata.range`, if it exists.
* docs(extui): rename box->msg, more->pager, prompt->dialogLuuk van Baal2025-06-13
| | | | | Includes breaking changes to the `opts` layout. "box" doesn't really describe anything other than a floating window so was an unwanted synonym.
* fix(extui): only append messages exceeding 'cmdheight' to "more"Luuk van Baal2025-06-13
| | | | | | | | | | | | Problem: 8defe1a declared the "more" window the most convenient place to route messages to if it is already open for msg.pos == 'cmd'. In usage, this doesn't appear to be the case. Appending messages as added in that commit is still useful, but should only be done for messages that spill 'cmdheight'. Solution: Only append messages exceeding 'cmdheight' to the more window. To do this, instead of immediately writing to the more buffer, write to the cmd buffer and calculate its height. Then copy the text and its highlights to the more buffer.
* vim-patch:91af4c4: runtime(doc): improve the wording of 'sts', 'varts' and ↵zeertzjq2025-06-13
| | | | | | | | | | 'varsts' values (#34480) closes: vim/vim#17522 https://github.com/vim/vim/commit/91af4c41809c4089d15857c1be13315b1969ea3b Co-authored-by: Damien Lejay <damien@lejay.be> Co-authored-by: Christian Brabandt <cb@256bit.org>
* fix(lsp): correct diagnostic data support and related info capabilities (#34454)Riley Bruins2025-06-12
|
* feat(lsp): <Plug> mapping for signature help cycling #34039Tiago Inaba2025-06-12
| | | | | | Replace direct function mappings with `<Plug>` mappings for cycling through overloaded signatures, providing better customization options for users. This change keeps the default mapping (`<C-s>`) for cycling if `<Plug>(nvim.lsp.ctrl-s)` is not mapped.
* feat(lsp): incremental selection via "textDocument/selectionRange" #34011Riley Bruins2025-06-12
| | | | Select outwards with "an" and inwards with "in" in Visual mode. Ranges are reset when leaving Visual mode.
* fix(lsp): _cancel_all_requests() tries to cancel completed requests #34105Andre Toerien2025-06-12
| | | | | | | | | | Problem: The cancel function returned by `vim.lsp.buf_request` tries to cancel all the requests, including those that have already been completed, causing "Cannot find request with id ... whilst attempting to cancel" errors to be logged when it is called. Solution: Only cancel the requests that are present in `client.requests`.
* vim-patch:053aee0: runtime(doc): add more pointers to 'completeopt' (#34460)zeertzjq2025-06-12
| | | | | | | | | | | | | | | | | Before this commit, I had trouble finding information about configuring the insert mode completion. In particular, it was not clear that the 'wildopt' config that I already had in my vimrc does not apply here. Also, `insert.txt` barely mentioned 'completeopt' except when describing popups (I was more interested in bash-like behavior where the unique prefix of all completions is completed first). I'm hoping these edits will make the relevant docs easier to find. closes: vim/vim#17515 https://github.com/vim/vim/commit/053aee01f7374fc8c985300399b1ad3b3626e40f Co-authored-by: Ilya Grigoriev <ilyagr@users.noreply.github.com>
* fix(lsp): announce diagnostic tag support (#34436)Riley Bruins2025-06-10
| | | | | This commit also adds a type annotation to the returned client capabilities table, because without it lua_ls does not provide autocompletion for the fields within the table.
* vim-patch:bfa1636: runtime(doc): update documentation on tabstop settings ↵zeertzjq2025-06-10
| | | | | | | | | | | | (#34433) Unify the treatment of tabstop, correct errors and deprecate smarttab usage. closes: vim/vim#17444 https://github.com/vim/vim/commit/bfa16364f104f336fc7407ee4533ae9045f040c4 Co-authored-by: Damien Lejay <damien@lejay.be>
* vim-patch:9.1.1446: filetype: cuda-gdb config files are not recognizedChristian Clason2025-06-10
| | | | | | | | | | | | Problem: filetype: cuda-gdb config files are not recognized Solution: detect .cuda-gdbinit and cuda-gdbinit files as gdb filetype (Wu Zhenyu) closes: vim/vim#17471 https://github.com/vim/vim/commit/601cfa9a2362ca14d83ddde392483bd6e3fbe39a Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* feat(lsp): workspace diagnostic support (#34262)Maria José Solano2025-06-09
| | | | | * refactor(lsp): remove underscore prefix from local variables * feat(lsp): workspace diagnostic support
* feat(lsp): static registration support (#34371)Maria José Solano2025-06-09
|
* feat(vim.fs): root() can specify "equal priority" #34276Siddhant Agarwal2025-06-09
|
* fix: `fn.exists()` typos (#34390)phanium2025-06-09
| | | | Problem: `exists()` checks should test for being equal to 1 rather than truthy, and extui check can be more restrictive. Solution: Adjust `exists()` guards to equal 1 and use `matchparen#CursorMoved`.
* fix(treesitter): ensure window is valid in async parsing #34385notomo2025-06-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Error occurs if window is invalid in the middle of parsing. Solution: Check if window is valid in parsing. - Error ``` vim.schedule callback: ...im/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:485: Invalid window id: 1037 stack traceback: [C]: in function 'nvim__redraw' ...im/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:485: in function 'cb' ...m/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:494: in function '_run_async_callbacks' ...m/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:550: in function <...m/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:529> ``` - Reproduce script ```lua local bufnr = vim.api.nvim_create_buf(false, true) local many_lines = vim.fn["repeat"]({ "local test = 'a'" }, 100000) vim.api.nvim_buf_set_lines(bufnr, 0, -1, false, many_lines) local window = vim.api.nvim_open_win(bufnr, true, { relative = "editor", row = 0, col = 0, width = 10, height = 10, }) vim.bo.filetype = "lua" vim.schedule(function() vim.api.nvim_win_close(window, true) end) ```
* fix(treesitter): support multiple `@injection.content` capturesRiley Bruins2025-06-08
| | | | | | | Before, only the last capture's range would be counted for injection. Now all captured ranges will be counted in the ranges array. This is more intuitive, and also provides a nice solution/alternative to the "scoped injections" issue.
* vim-patch:partial:8f7256a (#34368)zeertzjq2025-06-08
| | | | | | | vim-patch:partial:8f7256a: runtime(doc): fix some style issues and remove obsolete docs https://github.com/vim/vim/commit/8f7256a5ee5b827722de4e7524da1c2adb68bbae Co-authored-by: Hirohito Higashi <h.east.727@gmail.com>
* fix(treesitter): scope highlight state per window #34347Riley Bruins2025-06-07
| | | | | | | | | **Problem:** There is a lot of distracting highlight flickering when editing a buffer with multiple open windows. This is because the parsing/highlighting state is shared across all windows. **Solution:** Greatly reduce flicker in window splits by scoping the highlighter state object and the `parsing` state object to each individual window, so there is no cross-window interference.
* docs: lua, UI events #34261Justin M. Keyes2025-06-07
|
* fix: type fixesLewis Russell2025-06-06
| | | | Type fixes caught by emmylua
* refactor(treesitter): avoid unnecessarily copying treeRodrigodd2025-06-06
| | | | | node:tree() now already copies the tree before returning it, for memory safety reasons.
* fix(extui): use visible to determine active "more" (#34327)luukvbaal2025-06-06
| | | | | | | | | | | Problem: Current window is checked to determine whether "more" window is open. Making it the current window is scheduled in case the cmdwin is open so this can be too late. "cmdline_hide" may be emitted when the topline is temporarily invalid (after incsearch->restore_viewstate()). Solution: Use the window visibility to determine an active "more" window instead. Don't nvim__redraw->flush the "cmdline_hide" event (a normal will already happen).
* fix(lsp): only auto-detach lsp.config enabled clients #34325Kai-Hsiang Hsu2025-06-06
| | | | | | | Problem: A custom server (initialized through `vim.lsp.start`) gets unexpectedly detached. Solution: Only auto-detach the clients enabled through `vim.lsp.enable` to prevent unexpected behavior.
* fix(diagnostic): ensure autocmd always is always sent diagnosticsLewis Russell2025-06-05
|
* vim-patch:d6c9ac9: runtime(doc): clarify the effect of 'smarttab'zeertzjq2025-06-05
| | | | | | | | closes: vim/vim#17426 https://github.com/vim/vim/commit/d6c9ac97a009f7099b7d3636548aa3a4fabb5f1a Co-authored-by: Damien Lejay <damien@lejay.be>
* fix(extui): copy window config to new tabpage (#34308)luukvbaal2025-06-04
| | | | | | | | | Problem: When opening a new tabpage, extui windows are initialized with their default config. Window visiblity/dimensions on other tabpages may get out of sync with their buffer content. Solution: Copy the config of the window to the new tabpage. No longer keep track of the various windows on each tabpage. Close windows on inactive tabpages instead (moving them could be more efficient but is currently not supported in the API).
* docs: getreg() type #34215phanium2025-06-04
| | | | | | | | | ```lua ---@type string local _a = vim.fn.getreg('a', 1) ---@type string[] local _b = vim.fn.getreg('a', 1, 1) ```
* fix(vim.diagnostic): improve typingLewis Russell2025-06-03
| | | | | | | | | | | | | | | | | | Problem: `vim.diagnostic.set()` doesn't actually accept a list of `vim.Diagnostic` as internally `vim.diagnostic.set()` normalizes the diagnostics and this normalization is assumed throughout the module. Solution: - Add a new type `vim.Diagnostic.Set` which is the input to `vim.diagnostic.set()` - `col` is now an optional field and defaults to `0` to be consistent with `vim.diagnostic.match()`. - Change `table.insert(t, x)` to `table[#table + 1] = x` for improved type checking.
* fix(diagnostics): diagnostic just after EOL is not highlighted #34085Sergei Slipchenko2025-06-03
| | | | | | | | | | | | | | Fixes #34013 Problem: when diagnostic is set right after EOL, underline handler looks inconsistent compared to other handlers, visually underline is shown starting from the next line. On top of that it's also inconsistent with open_float and jump. Solution: clamp starting column position in underline handler to be right before EOL to make it visible and consistent with other handlers, open_float and jump.
* fix(glob): handling commas in letter pattern #34170Brynne Taylor2025-06-03
|
* vim-patch:bfeefc4: runtime(doc): clarify the effect of exclusive single char ↵zeertzjq2025-06-02
| | | | | | | | | selections (#34289) closes: vim/vim#17410 https://github.com/vim/vim/commit/bfeefc474a3ed25852491a93e1e5610774f4de8c Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.1409: using f-flag in 'complete' conflicts with Neovimzeertzjq2025-06-03
| | | | | | | | | | | | | | Problem: using f-flag in 'complete' conflicts with Neovims filename completion (glepnir, after v9.1.1301). Solution: use upper-case "F" flag for completion functions (Girish Palya). fixes: vim/vim#17347 closes: vim/vim#17378 https://github.com/vim/vim/commit/14f6da5ba8d602263fc7bf6cb899c8520f4c3060 Co-authored-by: Girish Palya <girishji@gmail.com>
generated by cgit (git 2.34.1) at 2026-10-24 15:03:27 +0000