aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* 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>
* vim-patch:9.1.1164: [security]: code execution with tar.vim and special ↵zeertzjq2025-03-02
| | | | | | | | | | | | | | crafted tar files (#32701) Problem: editing a special crafted tar file allows code execution (RyotaK, after 129a8446d23cd9cb4445fcfea259cba5e0487d29) Solution: escape the filename before feeding it to the `:read` command Github Advisory: https://github.com/vim/vim/security/advisories/GHSA-wfmf-8626-q3r3 https://github.com/vim/vim/commit/334a13bff78aa0ad206bc436885f63e3a0bab399 Co-authored-by: Christian Brabandt <cb@256bit.org>
* docs: misc #31996Justin M. Keyes2025-03-02
|
* feat(lua): don't complete private (_) fields after dot (.) #32690Maria José Solano2025-03-02
|
* feat(comment): allow commentstring to be determined from node metadataRiley Bruins2025-03-02
| | | | | | | | | | | **Problem:** Some weird languages have different comment syntax depending on the location in the code, and we do not have a way to determine the correct `commentstring` for these special cases. **Solution:** Allow queries to specify `commentstring` values in metadata, allowing users/`nvim-treesitter` to provide a better commenting experience without hugely increasing the scope of the code in core.
* build!: turn off translations by defaultdundargoc2025-03-02
| | | | | The translation step prolongs the build time too much to be enabled by default. Enable it by passing cmake flag `ENABLE_TRANSLATIONS=ON`.
* vim-patch:9.1.1161: preinsert requires bot "menu" and "menuone" to be setzeertzjq2025-03-02
| | | | | | | | | | | | Problem: preinsert requires bot "menu" and "menuone" to be set, but "menu" is redundant (after v9.1.1160) Solution: preinsert only requires menuone (glepnir) closes: vim/vim#16763 https://github.com/vim/vim/commit/94a045ed56d7616c0cd0080d3f308d6cf9fbe64c Co-authored-by: glepnir <glephunter@gmail.com>
* vim-patch:9.1.1160: Ctrl-Y does not work well with "preinsert" when ↵zeertzjq2025-03-02
| | | | | | | | | | | | | | | | | | | | | completing items Problem: The 'preinsert' feature requires Ctrl-Y to confirm insertion, but Ctrl-Y only works when the popup menu (pum) is displayed. Without enforcing this dependency, it could lead to confusing behavior or non-functional features. Solution: Modify ins_compl_has_preinsert() to check for both 'menu' and 'menuone' flags when 'preinsert' is set. Update documentation to clarify this requirement. This avoids adding complex conditional behaviors. (glepnir) fixes: vim/vim#16728 closes: vim/vim#16753 https://github.com/vim/vim/commit/a2c5559f297a18dc1ce3c4f1f9fd6204aed321c9 Co-authored-by: glepnir <glephunter@gmail.com>
* vim-patch:0b82054: runtime(lua): Improve 'include' and make '*expr' ↵brianhuster2025-03-02
| | | | | | | | | | | | | | | functions script-local - Prevent 'include' from matching variable assignments as calls to require() and others. - Use script-local functions for 'includeexpr' and 'foldexpr'. - Formatting fixes. closes: vim/vim#16746 https://github.com/vim/vim/commit/0b8205484b703b4a5a569cd1b0ed876bbb13901f Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* vim-patch:00a00f5: runtime(lua): Update lua ftplugin and documentationbrianhuster2025-03-02
| | | | | | | | | | | | | | | | | | | Problem: - The doc says the default `g:lua_subversion` is 2, but in fact it is 3 (see `runtime/syntax/lua.vim`) - `includeexpr` doesn't work with module in `init.lua` Solution: - Update documentation - Assign value to option `&include` - Add function `LuaInclude` and assign it to `l:&includeexpr` closes: vim/vim#16655 https://github.com/vim/vim/commit/00a00f5d3fc8dcf08e959c207a90f5902abc6a08 Co-authored-by: brianhuster <phambinhanctb2004@gmail.com> Co-authored-by: dkearns <dougkearns@gmail.com>
* vim-patch:8ac975d: runtime(tar): fix syntax error in tar.vimChristian Clason2025-03-01
| | | | | | https://github.com/vim/vim/commit/8ac975d97e153205a82ef0177013260f59cc6a2e Co-authored-by: Christian Brabandt <cb@256bit.org>
* feat(treesitter): add more metadata to `language.inspect()` (#32657)Lewis Russell2025-03-01
| | | | | | | | | Problem: No way to check the version of a treesitter parser. Solution: Add version metadata (ABI 15 parsers only) as well as parser state count and supertype information (ABI 15) in `vim.treesitter.language.inspect()`. Also graduate the `abi_version` field, as this is now the official upstream name. --------- Co-authored-by: Christian Clason <c.clason@uni-graz.at>
* vim-patch:56957ed: runtime(misc): add support for bzip3 to tar, vimball and ↵Christian Clason2025-03-01
| | | | | | | | | | | gzip plugins fixes: vim/vim#16751 closes: vim/vim#16755 https://github.com/vim/vim/commit/56957ed4109fb0c37922c6c37d5926cfe0a3313b Co-authored-by: Jim Zhou <jimzhouzzy@gmail.com>
* docs(Open): add reference in documentation (#32678)Luca Saccarola2025-02-28
|
* fix(marks): ineffective conceal_line callback optimization (#32662)luukvbaal2025-02-28
| | | | | | | Problem: _on_conceal_line callbacks are not invoked if callback has not let Nvim know it wants to receive them. But this may change on factors other than what is currently checked (changed buffer). Solution: Forego this optimization, callback is still guarded behind 'conceallevel'.
* vim-patch:8.2.4607: sourcing buffer lines may lead to errors for conflictszeertzjq2025-02-28
| | | | | | | | | | | | Problem: Sourcing buffer lines may lead to errors for conflicts. Solution: Add the ++clear argument. (Yegappan Lakshmanan, closes vim/vim#9991) https://github.com/vim/vim/commit/35dc17634dd6da5b90bd1b0160c4ed9e394f4b87 Documentation changes only. Vim9script is N/A. Cherry-pick another documentation change for :source from latest Vim. Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* vim-patch:8.2.4603: sourcing buffer lines is too complicatedzeertzjq2025-02-28
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Sourcing buffer lines is too complicated. Solution: Simplify the code. Make it possible to source Vim9 script lines. (Yegappan Lakshmanan, closes vim/vim#9974) https://github.com/vim/vim/commit/85b43c6cb7d56919e245622f4e42db6d8bee4194 This commit changes the behavior of sourcing buffer lines to always have a script ID, although sourcing the same buffer always produces the same script ID. vim-patch:9.1.0372: Calling CLEAR_FIELD() on the same struct twice Problem: Calling CLEAR_FIELD() on the same struct twice. Solution: Remove the second CLEAR_FIELD(). Move the assignment of cookie.sourceing_lnum (zeertzjq). closes: vim/vim#14627 https://github.com/vim/vim/commit/f68517c1671dfedcc1555da50bc0b3de6d2842f6 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* vim-patch:8.2.4594: need to write script to a file to be able to source themzeertzjq2025-02-28
| | | | | | | | | | | | | Problem: Need to write script to a file to be able to source them. Solution: Make ":source" use lines from the current buffer. (Yegappan Lakshmanan et al., closes vim/vim#9967) https://github.com/vim/vim/commit/36a5b6867bb6c0bd69c8da7d788000ab8a0b0ab0 Most code and test changes are reverted or modified again in patch 8.2.4603, so only port parts that are untouched in patch 8.2.4603. Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* fix(treesitter): correctly parse queries with combined injectionsRiley Bruins2025-02-28
|
* vim-patch:3d75ec7: runtime(compiler): improve svelte-checkChristian Clason2025-02-28
| | | | | | | | closes: vim/vim#16749 https://github.com/vim/vim/commit/3d75ec7401850e8a80ae7ab5ad1b84f47bc32095 Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* vim-patch:85a50fe: runtime(doc): fix confusing docs for 'completeitemalign' ↵zeertzjq2025-02-28
| | | | | | | (#32671) closes: vim/vim#16743 https://github.com/vim/vim/commit/85a50fe825ba11a35ce654f7313b4350e3ba4b52
* vim-patch:60bd140: runtime(vim): Update base-syntax, match Vim9 function ↵zeertzjq2025-02-28
| | | | | | | | | | | | | calls after "|" (#32670) Match Vim9 function calls after ex-bar. These are also currently matched but invalid syntax for legacy script. fixes: vim/vim#16721 closes: vim/vim#16747 https://github.com/vim/vim/commit/60bd140256be4f567c28c60eb84be72c19a164bd Co-authored-by: Doug Kearns <dougkearns@gmail.com>
generated by cgit (git 2.34.1) at 2025-07-13 15:11:55 +0000