aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* fix(lsp): handle non-existent configs in lsp.config/enableLewis Russell2025-03-12
|
* vim-patch:4fa2dd2: runtime(compiler): add comment for Dispatch (#32856)zeertzjq2025-03-12
| | | | | | | closes: vim/vim#16854 https://github.com/vim/vim/commit/4fa2dd2405a8d11bf1d1cb3553adb6fba53dc19f Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* feat(treesitter): allow `iter_captures` to accept `opts`Riley Bruins2025-03-12
| | | | | | This matches the `iter_captures` functionality to the `iter_matches` functionality, allowing it to specify a match limit and start depth for the query iterator.
* vim-patch:2347330: runtime(compiler): allow customizing exe and args for tsc ↵Muntasir Mahmud2025-03-12
| | | | | | | | | (#32853) closes: vim/vim#16853 https://github.com/vim/vim/commit/23473303b78d598a0f3c2f9370e011045093d3bd Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* feat(treesitter): allow passing lang to InspectTreeMaria José Solano2025-03-12
|
* vim-patch:a8aeeeb: runtime(tera): remove unwanted code and fix issues in ↵Muntasir Mahmud2025-03-12
| | | | | | | syntax script (#32848) closes: vim/vim#16857 https://github.com/vim/vim/commit/a8aeeeb9aa694f2052e904c3e02e525035e0701f
* vim-patch:0a336cc: runtime(doc): clarify that a umask is applied to mkdir() ↵zeertzjq2025-03-11
| | | | | | | | | (#32845) fixes: vim/vim#16849 https://github.com/vim/vim/commit/0a336ccb57003c44ba303ccc50cf50cb640c2309 Co-authored-by: Christian Brabandt <cb@256bit.org>
* refactor(lsp): rename `on_publish_diagnostics` parameter #32776Will Lillis2025-03-11
| | | | * fix(lsp): rename `on_publish_diagnostics` parameter: result->params * fix(colors): specify local var type to address lint failure
* feat(treesitter): allow disabling captures and patterns on TSQuery (#32790)Ian Chamberlain2025-03-11
| | | | | | | | | Problem: Cannot disable individual captures and patterns in treesitter queries. Solution: * Expose the corresponding tree-sitter API functions for `TSQuery` object. * Add documentation for `TSQuery`. * Return the pattern ID from `get_captures_at_pos()` (and hence `:Inspect!`).
* fix: warn when :InspectTree on buffer with no parser #32783phanium2025-03-11
| | | | | Problem: `InspectTree` error on buffer without ts parser attached. Solution: show a more correct warning.
* fix(lsp): improve LSP floating preview window cleanup #31353glepnir2025-03-11
| | | | | Problem: The current implementation creates a unique autocommand group for each floating preview window, which is inefficient and can lead to numerous autocommand groups. Solution: Use a single shared autocommand group with improved window validation to properly clean up LSP floating preview windows.
* fix(lsp): wrapped ctx in opts before passed to vim.lsp.completion.trigger #32837glepnir2025-03-11
| | | | | Problem: ctx is passed directly to M.trigger. In fact, it is a field of opts. Solution: wrapped in a table and passed to M.trigger.
* fix(events): fix incorrect capitalization of Cmdwin* events (#32813)zeertzjq2025-03-11
| | | | | | The name of Cmdwin* events were changed to CmdWin* in 8ed2dbf6e2802516501c11e72e5d6d977e6a07f3 without explanation. This commit changes them back. This doesn't affect the creation or execution of autocommands. It only affects the listing of autocommands.
* vim-patch:9.1.1194: filetype: false positive help filetype detectionzeertzjq2025-03-11
| | | | | | | | | | Problem: filetype: false positive help filetype detection Solution: Only detect a file as help if modeline appears either at start of line or is preceded by whitespace (zeertzjq). closes: vim/vim#16845 https://github.com/vim/vim/commit/6763b0ee95e7e66ab7992653fbba48691e803e70
* vim-patch:9.1.1191: tests: test for patch 9.1.1186 doesn't fail without the ↵zeertzjq2025-03-11
| | | | | | | | | | | patch Problem: Test for patch 9.1.1186 doesn't fail without the patch. Solution: Set 'nomodeline' in the test (zeertzjq). closes: vim/vim#16835 https://github.com/vim/vim/commit/d6c7913e24e07c1d0ea099cda85e0014e8627c5c
* vim-patch:9.1.1186: filetype: help files in git repos are not detectedzeertzjq2025-03-11
| | | | | | | | | | | | | | | | | | | | | | | | Problem: filetype: help files in git repos are not detected Solution: detect */doc/*.txt files as help if they end with a help modeline, even if 'modeline' is off Here's how I checked that this would still detect vim's own help files correctly: $ find . -type f -path '*/doc/*.txt' \ > -exec awk '{ } ENDFILE { print FILENAME ":" $0; }' '{}' + | > grep -v 'vim:.*\<\(ft\|filetype\)=help\>' ./src/libvterm/doc/seqs.txt: 23 DECSM 42 = DECNRCM, national/multinational character closes: vim/vim#16817 https://github.com/vim/vim/commit/16d6fff98ed3a9dfd34a41696b005b0c4c7800f8 Split the pattern into a Lua pattern for the first part and a Vim regex pattern for the second part, so that if the first part doesn't match there is no need to use the Vim regex. Co-authored-by: David Mandelberg <david@mandelberg.org>
* feat(checkhealth): group parsers by name and path in outputEike2025-03-10
| | | | | | | | | Problem: :checkhealth vim.treesitter sorts parser entries solely by path, splitting duplicates and reducing clarity. Solution: Sort entries first by name, then by path, so that duplicates are grouped.
* fix(lsp)!: pass buffer number to root_dir functionLewis Russell2025-03-10
| | | | | | | | | | | | | | Problem: The root dir function is not passed any context and can only assume the current buffer is the one being attached. The main use case is for getting the path of the buffer using `nvim_buf_get_name`. Solution: Pass the buffer number as the first argument.
* feat(lsp): support completion context #32793Maria José Solano2025-03-10
| | | | | | | | | Problem: vim.lsp.completion with "autotrigger" enabled, does not send completion context, even though it has all the necessary info. Solution: Include the context for "autotrigger". trigger() also optionally accepts context when manually invoked.
* fix(tohtml): disable modeline #32822altermo2025-03-10
| | | | | | | | Problem: Running :TOhtml with a file containing modeline may generate an invalid modeline in the output. Solution: Add `<!-- vim: set nomodeline: -->` to the output. Use vi-compatible modeline format ("set foo:"), to avoid the trailing `-->` being treated as part of the modeline.
* docs(vvars): vim.v.event.windows #32673Vlad2025-03-10
|
* fix(lua): types for vim.api.keyset.win_config #32700Tomasz N2025-03-10
|
* vim-patch:d49ba7b: runtime(sh): set b:match_skip to ignore matches for ↵zeertzjq2025-03-10
| | | | | | | | | | | matchit (#32812) related: vim/vim#16801 closes: chrisbra/matchit#50 closes: vim/vim#16834 https://github.com/vim/vim/commit/d49ba7b92a14e6f3c1c413d396df72d36e934f78 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:42e498d: runtime(plsql): move fold option from syntax to filetype ↵Christian Clason2025-03-10
| | | | | | | | | | | plugin closes: vim/vim#16838 https://github.com/vim/vim/commit/42e498d9c41a0260ccddceeb2927c18b508eff54 Co-authored-by: Lee Lindley <lee.lindley@gmail.com> Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* docs(api): show "since" in API docs #32806Justin M. Keyes2025-03-09
|
* fix(build): vimdoc tags are not validated #32801Justin M. Keyes2025-03-09
| | | | | | | | | Problem: "make lintdoc" is not validating vimdoc (:help) tags. Solution: - Call `lang_tree:parse()` to init the parser. - Load netrw 🤢 explicitly, since it was moved to `pack/dist/opt/`. - Fix invalid help tags.
* docs(highlight): collect all default highlight groupsChristian Clason2025-03-09
| | | | | | | | Problem: It's difficult for colorscheme authors to know which highlight groups should be defined. Solution: List and link to all built-in highlight group categories. Also remove outdated text on "preferred" and "secondary" groups.
* vim-patch:9.1.1188: runtime(tera): tera support can be improved (#32799)Muntasir Mahmud2025-03-09
| | | | | | | | | | Problem: runtime(tera): tera support can be improved Solution: update tera filetype plugin, include a tera syntax script update the filetype test, update makemenu and synmenu vim scripts (MuntasirSZN) closes: vim/vim#16830 vim/vim@14da0fb
* vim-patch:9.1.1187: matchparen plugin wrong highlights shell case statement ↵zeertzjq2025-03-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (#32798) Problem: matchparen plugin wrong highlights shell case statement (Swudu Susuwu) Solution: return early, if we are in a shSnglCase syntax element The shell syntax element "case $var in foobar)" uses closing parenthesis but there is no corresponding opening parenthesis for that syntax element. However matchparen is not aware of such things and will happily try to match just the next opening parenthesis. So let's just add a way to opt out for such cases. In this case, use the syntax state to check if the closing parenthesis belongs to the syntax item "shSnglCase" and if it is, do not try to find a corresponding opening parenthesis. Since inspecting the syntax state might be expensive, put the whole check behind a filetype test, so that matchparen will only perform this particular check, when it knows the current buffer is a "sh" filetype. fixes: vim/vim#16801 closes: vim/vim#16831 https://github.com/vim/vim/commit/9102ac11ab3938ec8c15bfebd00d2f91d3f1cd6c Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:d89770e: runtime(doc): use GNOME instead of Gnomezeertzjq2025-03-09
| | | | | | | | | | | | | | | It's called "GNOME Terminal" in https://gitlab.gnome.org/GNOME/gnome-terminal It's also called GNOME Terminal in English Wikipedia https://en.wikipedia.org/wiki/GNOME_Terminal and the Wikipedia pages of 8 other languages. Also, make line wrapping the same in insert.txt and cmdline.txt. closes: vim/vim#16832 https://github.com/vim/vim/commit/d89770eb987768aca78fef74d8d8601ce53fc435
* vim-patch:3d1a437: runtime(doc): warn users about potentially risky hotkeyzeertzjq2025-03-09
| | | | | | | | | | | | | | | Also, mention that CTRL-SHIFT-V might be mapped to paste text, similar to the note about CTRL-V. References: https://gitlab.gnome.org/GNOME/gnome-terminal/-/blob/2d7e9d78c9631be63b6b381f6966cb8808865ffb/src/org.gnome.Terminal.gschema.xml#L395-398 https://gitlab.gnome.org/chergert/ptyxis/-/blob/8942adde5b98c82c85238851743b371a034a1c1b/src/org.gnome.Ptyxis.gschema.xml.in#L529-L533 closes: vim/vim#16816 https://github.com/vim/vim/commit/3d1a437f1bb41933739445a8436fdc1902e4ea98 Co-authored-by: David Mandelberg <david@mandelberg.org>
* docs(events): document events that can always be nested (#32778)zeertzjq2025-03-09
| | | | | | | | | Follow-up to #32706 vim-patch:af05694: runtime(doc): CmdUndefined and FuncUndefined can always be nested closes: vim/vim#16825 https://github.com/vim/vim/commit/af056949007b2395b3f8ca8c7efb591fe9d4be9e
* vim-patch:62e8228: runtime(go): add 'keywordprg' and 'formatprg' to ftpluginChristian Clason2025-03-08
| | | | | | | | closes: vim/vim#16804 https://github.com/vim/vim/commit/62e822808e364c84e8abfbc4827bf6012e5b32e0 Co-authored-by: Phạm Bình An <phambinhanctb2004@gmail.com>
* docs: OSC 133 shell config #32771Justin M. Keyes2025-03-07
|
* fix(types): do not mark unstable API as privateLewis Russell2025-03-08
| | | | | These functions are allowed to be used downstream, they are just not API stable.
* vim-patch:6bdfeb0: runtime(vim): Update base-syntax, bug fixes (#32775)zeertzjq2025-03-07
| | | | | | | | | | | | - Allow trailing backslashes in option values. - Match :map-special modifier. - Match :map-arguments case-sensitively. - Remove <*Leader> from map modifier list and allow in RHS of a mapping. closes: vim/vim#16822 https://github.com/vim/vim/commit/6bdfeb099a4d814f2686af427360da13578906eb Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* feat(defaults): jump between :terminal shell prompts with ]]/[[ #32736Gregory Anders2025-03-07
|
* fix(lua): always use vim.inspect() for :lua= (#32715)zeertzjq2025-03-07
|
* fix(lsp): use unresolved code action when `codeAction/resolve` failsMaria José Solano2025-03-07
|
* vim-patch:9.1.1177: filetype: tera files not detectedChristian Clason2025-03-07
| | | | | | | | | | | | | Problem: filetype: tera files not detected Solution: detect '*.tera' files as tera filetype, include a simple filetype plugin (MuntasirSZN) closes: vim/vim#16806 https://github.com/vim/vim/commit/5daaf2326800ff0683a5be9a7f475667a4fc09db Co-authored-by: MuntasirSZN <muntasir.joypurhat@gmail.com>
* vim-patch:08a410f: runtime(vim): recognize <...> strings (and keys) for ↵zeertzjq2025-03-06
| | | | | | | | | | | 'keywordprg' (#32752) see :help E499 and :h key-notation closes: vim/vim#16795 https://github.com/vim/vim/commit/08a410f674a340f137623526bf8159d5a476f729 Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* vim-patch:9.1.1173: filetype: ABNF files are not detected (#32751)zeertzjq2025-03-06
| | | | | | | | | | | | | | | Problem: filetype: ABNF files are not detected Solution: detect '.abnf' file as abnf filetype and include an abnf syntax plugin (A4-Tacks). References: - RFC5234 - RFC7405 closes: vim/vim#16802 https://github.com/vim/vim/commit/9f827ec58728c4ea55a8d71d40a283ca2ce5b058 Co-authored-by: A4-Tacks <wdsjxhno1001@163.com>
* feat(lsp): support for resolving code action command (#32704)Maria José Solano2025-03-06
| | | | | * fix(lsp): don't call codeAction_resolve with commands * feat(lsp): support for resolving code action command
* fix(tui): remove DCS escaping in tmux (#32723)Gregory Anders2025-03-05
| | | | Per https://github.com/tmux/tmux/issues/4386, tmux does not support DCS responses, even if the initial request was escaped.
* vim-patch:4783a2c: runtime(doc): mention bzip3 in gzip plugin documentation ↵zeertzjq2025-03-05
| | | | | | | | | (#32742) closes: vim/vim#16800 https://github.com/vim/vim/commit/4783a2c073ecc075a6d1b23414901e78e1f18383 Co-authored-by: Jim Zhou <jimzhouzzy@gmail.com>
* feat(terminal)!: include cursor position in TermRequest event data (#31609)Gregory Anders2025-03-05
| | | | | | | | | | | | | | | | | | When a plugin registers a TermRequest handler there is currently no way for the handler to know where the terminal's cursor position was when the sequence was received. This is often useful information, e.g. for OSC 133 sequences which are used to annotate shell prompts. Modify the event data for the TermRequest autocommand to be a table instead of just a string. The "sequence" field of the table contains the sequence string and the "cursor" field contains the cursor position when the sequence was received. To maintain consistency between TermRequest and TermResponse (and to future proof the latter), TermResponse's event data is also updated to be a table with a "sequence" field. BREAKING CHANGE: event data for TermRequest and TermResponse is now a table
* fix(lsp): open_floating_preview() ignores max_height (#32716)Robert Muir2025-03-04
| | | | | | | Problem: After 47aaddfa the max_height option is no longer respected. Hover documentation and Signature help windows take up the entire text height. Solution: Compare to window's current height and only modify the height if it would reduce the height, not enlarge it.
* fix(diagnostic): virtual_lines diagnostic columns (#32703)James Trew2025-03-04
| | | | | When multiple diagnostics appear on a single line, the virtual lines for all diagnostics except the first were rendered with progressively fewer columns.
* vim-patch:659cb28: runtime(doc): fix typo "bet" in :h 'completeopt' (#32711)zeertzjq2025-03-04
| | | | | closes: vim/vim#16773 https://github.com/vim/vim/commit/659cb28c25b756e59c712c337f8b4650e85f8bcd
* vim-patch:9.1.1166: command-line auto-completion hard with wildmenuTomas Slusny2025-03-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: command-line auto-completion hard with wildmenu Solution: implement "noselect" wildoption value (Girish Palya) When `noselect` is present in `wildmode` and 'wildmenu' is enabled, the completion menu appears without pre-selecting the first item. This change makes it easier to implement command-line auto-completion, where the menu dynamically appears as characters are typed, and `<Tab>` can be used to manually select an item. This can be achieved by leveraging the `CmdlineChanged` event to insert `wildchar(m)`, triggering completion menu. Without this change, auto-completion using the 'wildmenu' mechanism is not feasible, as it automatically inserts the first match, preventing dynamic selection. The following Vimscript snippet demonstrates how to configure auto-completion using `noselect`: ```vim vim9script set wim=noselect:lastused,full wop=pum wcm=<C-@> wmnu autocmd CmdlineChanged : timer_start(0, function(CmdComplete, [getcmdline()])) def CmdComplete(cur_cmdline: string, timer: number) var [cmdline, curpos] = [getcmdline(), getcmdpos()] if cur_cmdline ==# cmdline # Avoid completing each character in keymaps and pasted text && !pumvisible() && curpos == cmdline->len() + 1 if cmdline[curpos - 2] =~ '[\w*/:]' # Reduce noise by completing only selected characters feedkeys("\<C-@>", "ti") set eventignore+=CmdlineChanged # Suppress redundant completion attempts timer_start(0, (_) => { getcmdline()->substitute('\%x00$', '', '')->setcmdline() # Remove <C-@> if no completion items exist set eventignore-=CmdlineChanged }) endif endif enddef ``` fixes: vim/vim#16551 closes: vim/vim#16759 https://github.com/vim/vim/commit/2bacc3e5fb3569e0fd98e129cb1e422ca18b80a6 Cherry-pick Wildmode_Tests() change from patch 9.0.0418. Co-authored-by: Girish Palya <girishji@gmail.com> Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
generated by cgit (git 2.34.1) at 2025-06-24 10:32:44 +0000