docs: misc #31867

justinmk · 2025-01-05T00:28:07Z

No description provided.

commit b288fa8d62c3f129d333d3ea6abc3234039cad37 Author: dundargoc <gocdundar@gmail.com> Date: Fri Jan 24 15:38:10 2025 +0100 build(bump_deps): abort if archive doesn't exist Also use git tag archive over commit sha if possible. commit 21aed725d2ac9ef5c6eb2ab631a6e1c3ad9b25fb Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 26 18:35:19 2025 +0100 vim-patch:db23436: runtime(asm): add byte directives to syntax script closes: vim/vim#16523 https://github.com/vim/vim/commit/db23436b92a1b08e91146ef462482f2c1a79dfe8 Co-authored-by: Nir Lichtman <nir@lichtman.org> commit c7d4a77ff9040c8b242f9d12a98472fe6217328c Author: glepnir <glephunter@gmail.com> Date: Mon Jan 27 08:02:33 2025 +0800 refactor(api): add missing cast #31960 commit 1759b7844a2d468310b6d0ceca899fec6f2d4b84 Author: Maria José Solano <majosolano99@gmail.com> Date: Sun Jan 26 15:33:03 2025 -0800 feat(diagnostic): virtual_lines #31959 commit d84a95da7e11555376a0ce60a0d4b5fbe15892d3 Author: glepnir <glephunter@gmail.com> Date: Mon Jan 27 07:28:33 2025 +0800 feat(api): nvim_get_autocmds filter by id#31549 Problem: nvim_get_autocmds cannot filter by id. Solution: Support it. commit b8e947ed4ed04f9aeef471f579451bbf2bb2993d Author: Christian Clason <c.clason@uni-graz.at> Date: Sat Jan 25 16:26:13 2025 +0100 vim-patch:fb49e3c: runtime(filetype): commit 99181205c5f8284a3 breaks V lang detection so make the regex more strict and have it check for a parenthesis. See: https://github.com/vlang/v/blob/master/examples/submodule/mymodules/submodule/sub_functions.v related: vim/vim#16513 https://github.com/vim/vim/commit/fb49e3cde79de4ce558c86d21a56eb9d60aeabd5 Co-authored-by: Christian Brabandt <cb@256bit.org> commit 974a3f7a438bb772bd681987b25214784c52c7da Author: Christian Clason <c.clason@uni-graz.at> Date: Sat Jan 25 15:41:29 2025 +0100 vim-patch:9918120: runtime(filetype): Improve Verilog detection by checking for modules definition While at it, also increase the maximum number of lines to check to 500. fixes: vim/vim#16513 https://github.com/vim/vim/commit/99181205c5f8284a30f839107a12932924168f17 Co-authored-by: Christian Brabandt <cb@256bit.org> commit e3e1c1e76581e63ea588a553f9b91f36a61d9d51 Author: Christian Clason <c.clason@uni-graz.at> Date: Sat Jan 25 15:40:47 2025 +0100 vim-patch:509a8d5: runtime(just): fix typo in syntax file closes: vim/vim#16515 https://github.com/vim/vim/commit/509a8d58f9a8ce00744114c1f21f0d951a559ecd Co-authored-by: Peter Benjamin <petermbenjamin@gmail.com> commit d4a65dad23b910ad0e5f44cc1720e8bd82bd749b Author: zeertzjq <zeertzjq@outlook.com> Date: Sat Jan 25 23:03:43 2025 +0800 vim-patch:9.1.1052: tests: off-by-one error in CheckCWD in test_debugger.vim (#32202) Problem: tests: off-by-one error in CheckCWD in test_debugger.vim Solution: Fix off-by-one in CheckCWD leading to local tests failure (Yee Cheng Chin) Vim's test_debugger's Test_debug_backtrace_level test will fail if you happen to run it in a Vim repository with full path of directory being exactly 29 characters (e.g. `/Users/bob/developing/src/vim`). The test does term dump comparison and the printout will overflow if the CWD is too long. It does have a function to skip to test if it detects that but it's off by one leading to this one situation where it will fail. The reason why the logic didn't account for this is that Vim's message printing will overflow the text if it prints a message at exactly the width of the terminal. This could be considered a bug / quirk but that will be another issue. closes: vim/vim#16517 https://github.com/vim/vim/commit/3acfbb4b548f4b1659ff1368a1b626cdd263acbe Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com> commit fb1740521aad48ba7ebd797042d869e3d649b91a Merge: 851137f679 689c23b2ac Author: zeertzjq <zeertzjq@outlook.com> Date: Sat Jan 25 22:57:59 2025 +0800 Merge pull request #32204 from zeertzjq/vim-9.1.1049 vim-patch:9.1.{1049,1053}: 'completeopt' "nosort" commit 689c23b2ac5c8cb5953e45f9f0cf6c369e8d88df Author: zeertzjq <zeertzjq@outlook.com> Date: Sat Jan 25 22:34:54 2025 +0800 vim-patch:9.1.1053: "nosort" enables fuzzy filtering even if "fuzzy" isn't in 'completeopt' Problem: "nosort" enables fuzzy filtering even if "fuzzy" isn't in 'completeopt' (after v9.1.1049) Solution: Only enable fuzzy filtering when "fuzzy" is in 'completeopt'. (zeertzjq) closes: vim/vim#16510 https://github.com/vim/vim/commit/d65aa1bbdb808ef8fecde6df240c48cc39a52a8e commit 63aa167f944b147b9d4b8c417a37f4beb212d984 Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 24 06:44:23 2025 +0800 vim-patch:9.1.1049: insert-completed items are always sorted Problem: insert-completed items are always sorted, although the LSP spec[1] standard defines sortText in the returned completionitem list. This means that the server has sorted the results. When fuzzy is enabled, this will break the server's sorting results. Solution: disable sorting of candidates when "nosort" is set in 'completeopt' [1] https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#completionItem closes: vim/vim#16501 https://github.com/vim/vim/commit/f400a0cc41113eb75516bdd7f38aeaa15208ba2c Co-authored-by: glepnir <glephunter@gmail.com> commit 851137f67905f6038e51b5b7d1490fbedea4faaa Author: phanium <91544758+phanen@users.noreply.github.com> Date: Sat Jan 25 12:05:47 2025 +0800 fix(log): log unset $TMPDIR at "debug" level #32137 commit 931ee5591fa764a769946318e05062098baf7c21 Author: georgev93 <39860568+georgev93@users.noreply.github.com> Date: Fri Jan 24 22:57:45 2025 -0500 feat(extmarks): virtual text can be right-aligned, truncated #31921 Problem: Right aligned virtual text can cover up buffer text if virtual text is too long Solution: An additional option for `virt_text_pos` called `eol_right_align` has been added to truncate virtual text if it would have otherwise covered up buffer text. This ensures the virtual text extends no further left than EOL. commit c6d2cbf8f51abfa0c9d244ef384a15b0b69e16c6 Author: Luuk van Baal <luukvbaal@gmail.com> Date: Thu Jan 23 12:42:38 2025 +0100 fix(lua): pop retval for fast context LuaRef Problem: nlua_call_ref_ctx() does not pop the return value in fast context that did not error. Solution: Fall through to end; calling nlua_call_pop_retval(). commit d98827b634af29d74079d1848dd5e8c5d2be1233 Author: Luuk van Baal <luukvbaal@gmail.com> Date: Wed Jan 22 23:13:40 2025 +0100 fix(messages): avoid empty msg_showmode with 'noshowmode' commit 0fd4ef5da7448fa3449643b23d6aa3af1640efe8 Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 19 17:36:35 2025 +0100 ci(tests): remove build-types jobs Problem: Some CI jobs are redundant: `RelWithDebInfo` is already tested on Linux-Arm64; `MinSizeRel` and Ninja Multi Config are not sufficiently relevant in practice to spend CI cycles on. Solution: Remove `build-types` job. commit 3702bcb139275beacb9d3d37f833b16d899f5013 Author: Christian Clason <c.clason@uni-graz.at> Date: Thu Jan 16 18:08:45 2025 +0100 ci(tests): add arm64 runner Problem: Linux `aarch64`/`arm64` builds are not tested. Solution: Add `ubuntu-arm` runners to test matrix (using `RelWithDebInfo` build). commit 2470db02c5136525b8abce1ee0889d94f8d81d98 Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 24 08:52:55 2025 +0800 vim-patch:partial:9.1.1050: too many strlen() calls in os_unix.c (#32188) Problem: too many strlen() calls in os_unix.c Solution: refactor os_unix.c and remove calls to strlen() (John Marriott) closes: vim/vim#16496 https://github.com/vim/vim/commit/efc41a5958bf25b352e0916af5f57dafbbb44f17 Omit os_expand_wildcards() change: Nvim's code is more complicated and harder to refactor. Co-authored-by: John Marriott <basilisk@internode.on.net> commit 8bc28978b632362ae658f8d4a6327e07a8b371b2 Author: luukvbaal <luukvbaal@gmail.com> Date: Fri Jan 24 00:42:24 2025 +0100 fix(column): apply custom highlight to last 'statuscolumn' segment (#32182) commit 2cd72258f6be0ea20f0341be9bc0d306c4533535 Author: Luuk van Baal <luukvbaal@gmail.com> Date: Tue Jan 21 11:15:31 2025 +0100 fix(mouse): 'statuscolumn' fold and popopmenu handling Problem: A right-click on the 'statuscolumn' does not open the popupmenu, even if a cell without a clickdef is clicked. Clicking the %C fold item does not open/close the fold. Solution: Open the popupmenu when there is no clickdef like right-clicking the sign/numbercolumn does. Fill "linebuf_vcol" when drawing the 'statuscolumn' to handle foldcolumn item clicks. commit a450fda4ededdd93e3dc571d82a6737f6b9d50d9 Author: Evgeni Chasnovski <evgeni.chasnovski@gmail.com> Date: Thu Jan 23 10:42:00 2025 +0200 fix(lsp): prefer `on_list` over `loclist` in default handler Problem: setting `loclist = true` makes `on_list` being ignored. This was not a problem before, but with `vim.lsp.buf.document_symbol` using `loclist = true` as default it is needed to explicitly pass `loclist = false` in order to use custom `on_list`. Solution: prefer `on_list` over `loclist` and document the latter as taking effect only in the default handler. commit 34d808b73cbcb0a43636d826282193ab1ca8c148 Author: Luuk van Baal <luukvbaal@gmail.com> Date: Thu Jan 16 18:10:22 2025 +0100 feat(api): combined highlights in nvim_eval_statusline() Problem: Combined highlighting was not applied to nvim_eval_statusline(), and 'statuscolumn' sign segment/numhl highlights. Solution: Add an additional `groups` element to the return value of `nvim_eval_statusline()->highlights`. This is an array of stacked highlight groups (highest priority last). Also resolve combined highlights for the 'statuscolumn' sign segment/numhl highlights. Expose/synchronize some drawline.c logic that is now mimicked in three different places. commit 8634bd46b26f28fa26950128b0cc585560bd6a9a Author: Christian Clason <c.clason@uni-graz.at> Date: Mon Jan 20 22:45:47 2025 +0100 vim-patch:9.1.1042: filetype: just files are not recognized Problem: filetype: just files are not recognized Solution: adjust filetype detection pattern, detect just shebang line, include just ftplugin, indent and syntax plugin (Peter Benjamin) closes: vim/vim#16466 https://github.com/vim/vim/commit/72755b3c8e91ec90447969b736f080e0de36003d Co-authored-by: Peter Benjamin <petermbenjamin@gmail.com> commit 28998e1f8a9cdca27ada7030757b7a47e99ce5b6 Author: zeertzjq <zeertzjq@outlook.com> Date: Thu Jan 23 16:33:41 2025 +0800 vim-patch:9.1.1045: filetype: N-Tripels and TriG files are not recognized (#32170) Problem: filetype: N-Tripels and TriG files are not recognized Solution: detect '*.nt' files as ntriples filetype and '*.trig' files as trig filetype (Gordian Dziwis) closes: vim/vim#16493 https://github.com/vim/vim/commit/c04334c33f543a6b84a4442cf235d84f5eaef6bb Co-authored-by: Gordian Dziwis <gordian@dziw.is> commit 4c9f3689a1c0646c8d743a2958af286b05c04ac5 Author: phanium <91544758+phanen@users.noreply.github.com> Date: Thu Jan 23 10:39:26 2025 +0800 fix(checkhealth): failed if 'lua' in plugin name commit a9c12d4c298813ed3aee36b2b4d5d0912c7201ea Author: zeertzjq <zeertzjq@outlook.com> Date: Thu Jan 23 08:12:10 2025 +0800 vim-patch:9.1.1048: crash after scrolling and pasting in silent Ex mode (#32168) Problem: Crash after scrolling and pasting in silent Ex mode. (fizz-is-on-the-way) Solution: Don't move cursor to line 0 when scrolling. (zeertzjq) closes: vim/vim#16506 https://github.com/vim/vim/commit/df098fedbc2c481e91ea7e6207dab90359a92cc3 commit fd55c7df6f7eb61c65e93c6dd8beffaeed93d2ed Author: zeertzjq <zeertzjq@outlook.com> Date: Thu Jan 23 08:11:53 2025 +0800 test(lua/hl_spec): set timeout for transient state (#32169) commit af0ef2ac9dd19b7c4005a3197334d3e7d554646c Author: Siddhant Agarwal <68201519+siddhantdev@users.noreply.github.com> Date: Wed Jan 22 21:16:24 2025 +0530 feat(lua): vim.hl.range() "timeout" #32012 Problem: `vim.hl.on_yank()` has a "timeout" behavior but this is not available for `vim.hl.range()`. Solution: Add `timeout` arg to `vim.hl.range()`. commit 34344b939c060d36db719f17088639744ca61c94 Author: luukvbaal <luukvbaal@gmail.com> Date: Wed Jan 22 16:36:57 2025 +0100 fix(editor): avoid scrolling :substitute confirm message #32149 Regression from 48e2a73. commit 22fd52325bf60cadaf24bca328a602764f53d6a9 Author: jdrouhard <john@drouhard.dev> Date: Wed Jan 22 07:02:30 2025 -0600 fix(inspector): update semantic token namespace (#32157) This updates the extmark namespace to search for when filtering out semantic tokens to match the new namespace style recently introduced. commit d46ebd2a74036a349606213fcd2a8b3530adebcf Author: zeertzjq <zeertzjq@outlook.com> Date: Wed Jan 22 17:10:29 2025 +0800 fix(startup): avoid crash with completion from -l script (#32160) Related #27764 commit a66f6add29fd8b2ee352c6089ceca6ab4f522385 Author: zeertzjq <zeertzjq@outlook.com> Date: Wed Jan 22 10:55:41 2025 +0800 vim-patch:9.1.1046: fuzzymatching doesn't prefer matching camelcase (#32155) Problem: fuzzymatching doesn't prefer matching camelcase (Tomasz N) Solution: Add extra score when case matches (glepnir) fixes: vim/vim#16434 closes: vim/vim#16439 https://github.com/vim/vim/commit/9dfc7e5e6169594f6f4607ef1ba9dd347a9194d2 Co-authored-by: glepnir <glephunter@gmail.com> commit a8b6fa07c4d9143f3bd279ce8fd87e8121da16e1 Author: zeertzjq <zeertzjq@outlook.com> Date: Wed Jan 22 09:28:27 2025 +0800 fix(search): avoid quadratic time complexity when computing fuzzy score (#32153) commit 3a25995f304039517b99b8c7d79654adf65c7562 Merge: d7aba51d39 06a1f82f1c Author: zeertzjq <zeertzjq@outlook.com> Date: Tue Jan 21 22:50:39 2025 +0800 Merge pull request #32144 from zeertzjq/termkey-x1-x2 feat(tui/terminal): support X1 and X2 mouse events commit 06a1f82f1cc37225b6acc46e63bd2eb36e034b1a Author: zeertzjq <zeertzjq@outlook.com> Date: Tue Jan 21 21:00:56 2025 +0800 feat(terminal): forward X1 and X2 mouse events Ref: https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Other-buttons commit 44dbfcfba4b09bb0e38f4a3f1960fa256a7bed71 Author: zeertzjq <zeertzjq@outlook.com> Date: Tue Jan 21 20:50:33 2025 +0800 feat(tui): recognize X1 and X2 mouse events Ref: https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Other-buttons commit d7aba51d39c7409ef388ed7cffe3e31d9fcec163 Merge: 05435bf105 4cced601c8 Author: bfredl <bjorn.linse@gmail.com> Date: Tue Jan 21 12:32:20 2025 +0100 Merge pull request #32098 from bfredl/multihl_group feat(extmark): stack multiple highlight groups in `hl_group` commit 4cced601c8cdfd6253266b035667dd0383a07ebe Author: bfredl <bjorn.linse@gmail.com> Date: Fri Jan 17 13:44:07 2025 +0100 feat(extmark): stack multiple highlight groups in `hl_group` This has been possible in the "backend" for a while but API was missing. Followup: we will need a `details2=true` mode for `nvim_get_hl_id_by_name` to return information in a way forward compatible with even further enhancements. commit 05435bf10585e7f850ff44acd63446fbcc56bfe5 Author: zeertzjq <zeertzjq@outlook.com> Date: Tue Jan 21 08:10:14 2025 +0800 vim-patch:c273f1a: runtime(vim): Update base-syntax, match ternary and falsy operators (#32132) fixes: vim/vim#14423 fixes: vim/vim#16227 closes: vim/vim#16484 https://github.com/vim/vim/commit/c273f1ac770e86767206c8193bab659b25d3b41b Co-authored-by: Doug Kearns <dougkearns@gmail.com> commit 855a2a75e6f7d08376c221a46e0179e5c76176ec Author: Christian Clason <c.clason@uni-graz.at> Date: Mon Jan 20 22:44:56 2025 +0100 vim-patch:4335fcf: runtime(kconfig): updated ftplugin and syntax script https://github.com/vim/vim/commit/4335fcfed1b0a29c07b10f97d1f309dd8f964de6 Co-authored-by: Christian Brabandt <cb@256bit.org> commit f50f86b9ff5dd2aab7838801d3c1cad898ea0c77 Author: Konrad Malik <konrad.malik@gmail.com> Date: Mon Jan 20 17:17:46 2025 +0100 fix(treesitter): compute folds on_changedtree only if not nil commit 0bc75ac78eba28c22d0facd3743fbe2dc573ee90 Author: dundargoc <gocdundar@gmail.com> Date: Mon Jan 20 17:34:53 2025 +0100 ci(news): treat deprecated.txt as part of news.txt This is because we reference to deprecated.txt from news.txt, so deprecation news updates are made only in deprecated.txt. commit 20e16c1c49ea946203f13a7e77c9b20ff9749659 Merge: 5b1136a99c 19b25f3fea Author: bfredl <bjorn.linse@gmail.com> Date: Mon Jan 20 15:42:56 2025 +0100 Merge pull request #32099 from bfredl/no_bufhl feat(api): deprecate nvim_buf_add_highlight() commit 5b1136a99c7fc6db4cfe6865b72c069a4697c1a5 Author: Donatas <contactdonatas@gmail.com> Date: Mon Jan 20 16:40:26 2025 +0200 feat(inccommand): preview 'nomodifiable' buffers #32034 Problem: Incremental preview is not allowed on 'nomodifiable' buffers. Solution: - Allow preview on 'nomodifiable' buffers. - Restore the 'modifiable' option in case the preview function changes it. commit 92556be33d04668c58a37794de5562af6297b3ac Author: Luuk van Baal <luukvbaal@gmail.com> Date: Thu Jan 16 16:03:06 2025 +0100 fix(messages): compute msg_col after last newline in ext_messages Problem: We want to keep track of the current message column, which is done very rudimentary for ext_messages; only checking if the message ends in a newline to reset the column, while computing the entire cellwidth of the message, which may contain (multiple) newlines not necessarily at the end (since 21718c6). This introduced a noticeable delay for large messages (e.g. :=vim). Solution: Calculate the cellwidth of the message after the last newline. Use it to keep track of the current message column. This might not be a functional change currently, since it only affects messages with (multiple) newlines not at the end of a message, which I don't think we emit internally, and msg_col is reset for a new kind. It does fix the performance problem. commit ded15ca8c210965442d39ab214d4838b80a3fdc6 Author: Konrad Malik <konrad.malik@gmail.com> Date: Mon Jan 20 15:10:00 2025 +0100 fix: completion.enable(false,...) deletes invalid augroup #32121 Problem: vim.lsp.completion.enable(true, client.id, bufnr) vim.lsp.completion.enable(false, client.id, bufnr) Error detected while processing LspDetach Autocommands for "*": Error executing lua callback: …/lsp/completion.lua:701: Vim:E367: No such group: "vim/lsp/completion-22" stack traceback: [C]: in function 'nvim_del_augroup_by_name' …/lsp/completion.lua:701: in function 'disable_completions' …/lsp/completion.lua:724: in function 'enable' Solution: Delete the correct augroup. commit 8a236c242a76825a6a9266feda45794c7328c807 Author: Guilherme Soares <48023091+guilhas07@users.noreply.github.com> Date: Mon Jan 20 13:00:13 2025 +0000 fix(lsp): set floating window filetype after setup #32112 Problem: The filetype for the floating window buffer is being set before its context is fully initialized. This results in `FileType` events not receiving the correct context. Solution: Set the filetype after the floating preview window and its buffer variables are fully configured to ensure proper context is provided. commit 19b25f3feacfedc18a57eb2a1368a1ed07ac5faa Author: bfredl <bjorn.linse@gmail.com> Date: Sun Jan 19 13:30:11 2025 +0100 feat(api): deprecate nvim_buf_add_highlight() This was kept for a while as it was a useful short hand and initially matched what highlights what actually properly implemented. But now |vim.hl.range()| is a better high-level shorthand with full support for native multi-line ranges. commit 27c88069538bf64dace1ed39512d914e88615ac1 Author: Jaehwang Jung <tomtomjhj@gmail.com> Date: Mon Jan 20 21:17:36 2025 +0900 docs(treesitter): expose LanguageTree:parent() #32108 Plugins may want to climb up the LanguageTree. Also add missing type annotations for other methods. commit 71922cd1dc3bb6e040d7ab1ecd4d457f979a98fa Merge: 5b025b499e 59da82abd9 Author: bfredl <bjorn.linse@gmail.com> Date: Mon Jan 20 11:02:58 2025 +0100 Merge pull request #31597 from bfredl/deletionism fix(wininfo): when freeing windows, free the lowest priority wininfo commit 5b025b499ec430f1733409f0fb5ba3f88ce25a88 Author: Christian Clason <c.clason@uni-graz.at> Date: Sat Jan 18 10:42:11 2025 +0100 vim-patch:9.1.1030: filetype: setting bash filetype is backwards incompatible Problem: filetype: setting bash filetype is backwards incompatible Solution: revert patch v9.1.0965, detect bash scripts again as sh filetype This reverts commit b9b762c21f2b61e0e7d8fee43d4d3dc8ecffd721. related: vim/vim#16309 https://github.com/vim/vim/commit/727c567a0934643e2d6e1dd92d4e636b17d9067f Co-authored-by: Christian Brabandt <cb@256bit.org> vim-patch:9.1.1033: tests: shaderslang was removed from test_filetype erroneously Problem: tests: shaderslang was removed from test_filetype erroneously (Christian Clason, after v9.1.1030) Solution: restore the test https://github.com/vim/vim/commit/1d2867df0c5dfa3d2444229f9e4b23d6ff935956 Co-authored-by: Christian Brabandt <cb@256bit.org> commit b172dd57faac8de98291b644c0b0e1ee6d4691e0 Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 19 16:50:38 2025 +0100 vim-patch:2cb8246: runtime(tex): add texEmphStyle to texMatchGroup in syntax script fixes: vim/vim#16228 https://github.com/vim/vim/commit/2cb8246eb969594a6969b03dcf8ea89aa7deda6e Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Github User JordL commit 4dc2e016dacfbbeaa6671a23f7ce8a4bb06c853f Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 19 16:51:11 2025 +0100 vim-patch:d402ba8: runtime(netrw): upstream snapshot of v175 Relevant commits: - release: netrw v175 - fix: prevent netrw to load into the built-in terminal - fix: restore correctly cpo settings - fix(docs): mispelled original authors name - chore: move viml files to new formatting standard fixes: vim/vim#16463 closes: vim/vim#16465 https://github.com/vim/vim/commit/d402ba81e256b21e73a98ec809bd4a9482613553 Co-authored-by: Luca Saccarola <github.e41mv@aleeas.com> commit de83cc5842c94d84ef5b876b7cfb06372c7e7b9c Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 19 17:05:32 2025 +0100 fix(netrw): re-add missing comment marker in syntax file commit 5f527f24f0ea89e9071e065530cbed449507df5c Author: Mathias Fussenegger <f.mathias@zignar.net> Date: Sun Jan 19 21:49:02 2025 +0100 fix(lsp): don't use completion filterText if prefix is empty Follow up to https://github.com/neovim/neovim/pull/32072 If there is no prefix (e.g. at the start of word boundary or a line), it always used the `filterText` because the `match` function always returned false. commit d56ba71af11c9048c9085e4f66a47947770bdb29 Author: Yochem van Rosmalen <git@yochem.nl> Date: Sun Jan 19 22:08:10 2025 +0100 fix(lsp): document_symbol uses loclist by default #32070 Problem: Not able to open document symbols for different buffers Solution: Use the location list as default. To switch back to previous behavior (qflist): vim.lsp.buf.document_symbol({ loclist = false }) Fixes: #31832 commit a6f219b06bebf5878b970bebf53db7b942fe8731 Author: deepsghimire <70006817+deepsghimire@users.noreply.github.com> Date: Mon Jan 20 01:22:04 2025 +0545 fix(log): unintuitive message for undefined $TMPDIR commit 6696ea7f103814d3d5700107546280bf50a4004a Author: Jaehwang Jung <tomtomjhj@gmail.com> Date: Sun Jan 19 00:07:47 2025 +0900 fix(treesitter): clean up parsing queue commit ee54069d1d279b351e5569cb205b1ee111ec0dc5 Author: zeertzjq <zeertzjq@outlook.com> Date: Sun Jan 19 22:14:52 2025 +0800 vim-patch:8dec6c2: runtime(vim): Update base-syntax, fix is/isnot operator matching (#32100) - Match is? and isnot? operators. - Limit other comparison operators to one match modifier rather than two. closes: vim/vim#16482 https://github.com/vim/vim/commit/8dec6c2e6c2b5157334398e2e6ab7daa91999d80 Co-authored-by: Doug Kearns <dougkearns@gmail.com> commit 71507281fb86deaaa7f47460e8c7a503b46663f6 Author: Devon Gardner <devon@goosur.com> Date: Sat Jan 18 19:49:53 2025 -0500 fix(coverity/530826): validate_opt_idx unchecked negative idx (#32081) Problem: opt_idx possible negative value used as index Solution: check opt_idx not less than zero (kOptInvalid) commit a5b1b83a2693ffa7a5a0a22b3693d36ea60051be Author: 林玮 (Jade Lin) <linw1995@icloud.com> Date: Sat Jan 18 16:40:40 2025 +0800 fix(lua): prevent SIGSEGV when lua error is NULL in libuv_worker Problem: Calling `xstrdup` with a NULL pointer causes a SIGSEGV if `lua_tostring` returns NULL in `nlua_luv_thread_common_cfpcall`. Crash stack trace: - `_platform_strlen` → `xstrdup` (memory.c:469) - `nlua_luv_thread_common_cfpcall` (executor.c:281) Solution: Check if `lua_tostring` returns NULL and pass NULL to `event_create` to avoid the crash. commit 51ccd12b3dbc50300e83f503426abbcb605efcea Author: Gregory Anders <greg@gpanders.com> Date: Sat Jan 18 07:43:21 2025 -0600 fix(diagnostic)!: make virtual text handler opt-in (#32079) Making this opt-out (on by default) was the wrong choice from the beginning. It is too visually noisy to be enabled by default. BREAKING CHANGE: Users must opt-in to the diagnostic virtual text handler by adding vim.diagnostic.config({ virtual_text = true }) to their config. commit 954d4969c991be1a758c121be6f7d811b5e5cea1 Author: Christian Clason <c.clason@uni-graz.at> Date: Sat Jan 18 10:58:14 2025 +0100 vim-patch:e064051: runtime(c): add new constexpr keyword to syntax file (C23) closes: vim/vim#16471 https://github.com/vim/vim/commit/e06405181a6189aa56e917c1a7e5090a33b07a8a Co-authored-by: Doug Kearns <dougkearns@gmail.com> commit 7d04ebd43c29a5f0663e6a2a9c5b54f064247d01 Author: Christian Clason <c.clason@uni-graz.at> Date: Sat Jan 18 10:46:33 2025 +0100 vim-patch:54cb514: runtime(sh): update syntax script - remove duplicated keywords - add bash coproc and COPROC_PID keywords https://github.com/vim/vim/commit/54cb514c9a8320d77650a63f0f7405aa8cc5b0d7 Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com> commit 27da6f77578c10090ad33a94ce26006a79784ee3 Author: dundargoc <gocdundar@gmail.com> Date: Sun Jan 12 13:10:48 2025 +0100 refactor: simplify bump_deps.lua Simplify usage and remove redundant flags and code. commit e962167245755e900a7bd154075106026dbb4eff Author: Christian Clason <c.clason@uni-graz.at> Date: Fri Jan 17 13:48:47 2025 +0100 vim-patch:9cfdabb: runtime(netrw): change netrw maintainer Dr. Chip retired some time ago and is no longer maintaining the netrw plugin. However as a runtime plugin distributed by Vim, it important to maintain the netrw plugin in the future and fix bugs as they are reported. So, split out the netrw plugin as an additional package, however include some stubs to make sure the plugin is still loaded by default and the documentation is accessible as well. closes: vim/vim#16368 https://github.com/vim/vim/commit/9cfdabb074feefc9848e9f7a4538f201e28c7f06 Co-authored-by: Luca Saccarola <github.e41mv@aleeas.com> commit 136cb642a0022fd005481e729dcc917552103322 Author: Christian Clason <c.clason@uni-graz.at> Date: Fri Jan 17 18:42:07 2025 +0100 vim-patch:c2a967a: runtime(c): Update syntax and ftplugin files - highlight more C keywords, including some from C23 Conditionally highlight C23 features: - #embed, #elifdef and #elifndef preprocessor directives - predefined macros - UTF-8 character constants - binary integer constants, _BitInt literals, and digit separators - nullptr_t type and associated constant - decimal real floating-point, bit precise and char types - typeof operators Matchit: - update for new preprocessor directives fixes: vim/vim#13667 fixes: vim/vim#13679 closes: vim/vim#12984 https://github.com/vim/vim/commit/c2a967a1b9adca6c929e3dc5c218dfada00059b6 Co-authored-by: Doug Kearns <dougkearns@gmail.com> Co-authored-by: Albin Ahlbäck <albin.ahlback@gmail.com> commit c9000a6b13fd6695f6e28a890b82b490a123f25e Author: zeertzjq <zeertzjq@outlook.com> Date: Sat Jan 18 10:03:13 2025 +0800 vim-patch:9.1.1028: too many strlen() calls in screen.c (#32083) Problem: too many strlen() calls in screen.c Solution: refactor screen.c and remove calls to strlen(), verify that leadmultispace != NULL (John Marriott) closes: vim/vim#16460 https://github.com/vim/vim/commit/c15de972e8131def2f506bb9eb6b306ca089629c Co-authored-by: John Marriott <basilisk@internode.on.net> commit c6cc937512f59af12fd1b15ca4f7a11288f28ca0 Author: Yochem van Rosmalen <git@yochem.nl> Date: Fri Jan 17 23:56:30 2025 +0100 docs: change augroup names to new convention #32061 Ref: 09e01437c968be4c6e9f6bb3ac8811108c58008c commit b9e6fa7ec81c463d77cc919392b52f6df2d8d304 Author: Mathias Fussenegger <f.mathias@zignar.net> Date: Fri Jan 17 15:27:50 2025 +0100 fix(lsp): use filterText as word if textEdit/label doesn't match Problem: With language servers like lemminx, completing xml tags like `<mo` first shows the right candidates (`modules`) but after typing `d` the candidates disappear. This is because the server returns: [...] filterText = "<module", label = "module", textEdit = { newText = "<module>$1</module>$0", Which resulted in `module` being used as `word`, and `module` doesn't match the prefix `<mo`. Typing `d` causes the `complete()` filtering mechanism to kick in and remove the entry. Solution: Use `<module` from the `filterText` as `word` if the textEdit/label heuristic doesn't match. commit 3530182ba491ba8663b40bdff0c044d74e89bb82 Author: Christian Clason <c.clason@uni-graz.at> Date: Fri Jan 17 13:46:58 2025 +0100 vim-patch:9.1.1026: filetype: swc configuration files are not recognized Problem: filetype: swc configuration files are not recognized Solution: detect .swcrc files as json filetype (Marces Engel) References: https://swc.rs/docs/configuration/swcrc closes: vim/vim#16462 https://github.com/vim/vim/commit/3a738fccaaf6737c91641856ea00579dbe68bd4e Co-authored-by: Marces Engel <marces@facemurphy.com> commit 97d58553515552afbac2999409e9bbf9a338dfb0 Author: Christian Clason <c.clason@uni-graz.at> Date: Fri Jan 17 10:48:37 2025 +0100 docs(gh): use new issue types commit 5dd60e01ace2621f2307eebeb92e9e7351210d3a Author: Luuk van Baal <luukvbaal@gmail.com> Date: Thu Jan 16 01:11:07 2025 +0100 refactor(cmdline): more idiomatic way to avoid cmdline_show Problem: Fix applied in #32033 can be more idiomatic. Solution: Unset redraw_state instead of cmdbuff. commit 7ce27381fb49ac7d6ef1e115c3952f998e979b15 Author: Luuk van Baal <luukvbaal@gmail.com> Date: Thu Jan 16 08:47:29 2025 +0100 fix(messages): lsp window/showMessage is not an error Ref https://github.com/neovim/neovim/discussions/32015 commit ac3859a4410e50794a083f23796e4f8ae2a24b04 Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 17 09:09:47 2025 +0800 vim-patch:a234a46: runtime(doc): fix typo in usr_02.txt (#32063) fixes: vim/vim#16455 https://github.com/vim/vim/commit/a234a46651ef174549792bd64d4bef64a32072bb Co-authored-by: Christian Brabandt <cb@256bit.org> commit cd92924896ab6edeb4d3219befc59ac52a60bcf2 Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 17 08:53:10 2025 +0800 vim-patch:9.1.1021: string might be used without a trailing NUL (#32062) Problem: string might be used without a trailing NUL (after v9.1.0997) Solution: Make sure that the buffer is NUL terminated closes: vim/vim#16457 https://github.com/vim/vim/commit/70dfc374ec72634a0a61aea8344178779675d516 Co-authored-by: John Marriott <basilisk@internode.on.net> commit 0d3a8e8c1a7778c6c79658f26ba492a5f4a17d18 Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 17 08:38:58 2025 +0800 vim-patch:9.1.1020: no way to get current selected item in a async context (#32056) Problem: no way to get current selected item in a async context Solution: add completed flag to show the entries of currently selected index item (glepnir) closes: vim/vim#16451 https://github.com/vim/vim/commit/037b028a2219d09bc97be04b300b2c0490c4268d Co-authored-by: glepnir <glephunter@gmail.com> commit bf098c12e3078df49fd7dee5ba7c2100a211d4c8 Merge: fb564ddff0 819337a13f Author: Gregory Anders <greg@gpanders.com> Date: Thu Jan 16 18:33:22 2025 -0600 Merge pull request #32038 from gpanders/push-nsrttwwnsqvm feat(terminal): add support for kitty keyboard protocol commit 819337a13f73bb9dcd82fd51f81f062bd69ab6db Author: Gregory Anders <greg@gpanders.com> Date: Wed Jan 15 13:08:18 2025 -0600 test: use esc sequences in vterm unit tests commit 6f0bde11ccd82d257fcda25ecad26227eba3335e Author: Gregory Anders <greg@gpanders.com> Date: Wed Jan 15 11:07:51 2025 -0600 feat(terminal): add support for kitty keyboard protocol This commit adds basic support for the kitty keyboard protocol to Neovim's builtin terminal. For now only the first mode ("Disambiguate escape codes") is supported. commit fb564ddff0b4ec9dad5afa7548777af1c3044273 Author: Lewis Russell <lewis6991@gmail.com> Date: Thu Jan 16 20:53:17 2025 +0000 refactor(options): generic expand and did_set callbacks (#32011) * refactor(options): generic expand and did_set callbacks Problem: Many options have similar callbacks to check the values are valid. Solution: Generalize these callbacks into a single function that reads the option table. * refactor: gen_options.lua refactor: gen_options.lua - inline get_cond * refactor(options): use a simpler format for the common default commit 92d3bf101d07d52cfbd4c22e6e06251897adda34 Merge: 718e165360 47a4e42392 Author: zeertzjq <zeertzjq@outlook.com> Date: Thu Jan 16 12:20:33 2025 +0800 Merge pull request #32051 from zeertzjq/vim-9.1.1013 vim-patch:9.1.{1013,1017} commit 47a4e4239203fe96d404874bdc1ea6910f72b695 Author: zeertzjq <zeertzjq@outlook.com> Date: Thu Jan 16 09:35:52 2025 +0800 vim-patch:9.1.1017: Vim9: Patch 9.1.1013 causes a few problems Problem: Vim9: Patch 9.1.1013 causes a few problems Solution: Translate the function name only when it is a string (Yegappan Lakshmanan) fixes: vim/vim#16453 closes: vim/vim#16450 https://github.com/vim/vim/commit/9904cbca4132f7376246a1a31305eb53e9530023 Cherry-pick call() change from patch 9.0.0345. Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com> commit f8680d009741d01e137aeb2232aa7e033cd70d7b Author: zeertzjq <zeertzjq@outlook.com> Date: Thu Jan 16 09:27:08 2025 +0800 vim-patch:9.1.1013: Vim9: Regression caused by patch v9.1.0646 Problem: Vim9: Regression caused by patch v9.1.0646 Solution: Translate the function name before invoking it in call() (Yegappan Lakshmanan) fixes: vim/vim#16430 closes: vim/vim#16445 https://github.com/vim/vim/commit/6289f9159102e0855bedc566636b5e7ca6ced72c N/A patch: vim-patch:8.2.4176: Vim9: cannot use imported function with call() Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com> commit 718e16536052c0e75de61a32ef237a9e87fc03f2 Author: zeertzjq <zeertzjq@outlook.com> Date: Thu Jan 16 09:16:25 2025 +0800 vim-patch:9.1.1018: v9.1.0743 causes regression with diff mode (#32047) Problem: v9.1.0743 causes regression with diff mode Solution: Fix the regression with overlapping regions closes: vim/vim#16454 https://github.com/vim/vim/commit/01f6509fb2de1627cc4ec2c109cd0aa2e3346d50 Co-authored-by: Yukihiro Nakadaira <yukihiro.nakadaira@gmail.com> commit 524be56042335db589b9fe62dfdae39be3f69a15 Author: Christian Clason <c.clason@uni-graz.at> Date: Thu Jan 16 00:34:25 2025 +0100 vim-patch:9.1.1019: filetype: fd ignore files are not recognized (#32042) Problem: filetype: fd ignore files are not recognized Solution: detect .fdignore files as gitignore filetype closes: vim/vim#16444 https://github.com/vim/vim/commit/3058087f6f04be788118e94e942e0f0c9fca25f0 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu> commit f0fdc1de6c950a015ada9550473aedde43b946ce Author: Christian Clason <c.clason@uni-graz.at> Date: Wed Jan 15 19:24:48 2025 +0100 build(deps): bump libuv to v1.50.0 commit 7c652242579b6f734b57de106afbe1d5c32ed2fd Author: dundargoc <gocdundar@gmail.com> Date: Wed Jan 15 18:18:04 2025 +0100 build: fix lint error on macos commit bbf36ef8ef86534e317e4e0153730a40ae4c936e Author: luukvbaal <luukvbaal@gmail.com> Date: Wed Jan 15 15:55:21 2025 +0100 fix(cmdline): prevent cmdline_show events after exiting cmdline #32033 Problem: If a (vim.ui_attach) cmdline_hide callback triggers a redraw, it may cause cmdline_show events for an already exited cmdline. Solution: Avoid emitting cmdline_show event when ccline.cmdbuff is already NULL. Unset ccline.cmdbuff before emitting cmdline_hide. commit 5cc93ef4729c65d6a539c8d0a8a2bf767cf17ced Author: luukvbaal <luukvbaal@gmail.com> Date: Wed Jan 15 11:38:45 2025 +0100 fix(marks): revise metadata for start mark of revalidated pair #32017 Problem: Metadata may be revised for end mark of a revalidated pair. Solution: Revise metadata for start mark of a revalidated pair. commit 09bcb310681e3b87d5b8c5eb547b182554cff7b4 Author: Evgeni Chasnovski <evgeni.chasnovski@gmail.com> Date: Wed Jan 15 12:36:00 2025 +0200 fix(docs): replace `yxx` mappings with `g==` #31947 Problem: `yx` uses "y" prefix, which shadows a builtin operator. Solution: Use `g=` (in the form of `g==` currently), drawing from precedent of CTRL-= and 'tpope/vim-scriptease'. commit 9552fe7ef907c5c8164abb50699e97d03de1285a Merge: 3ee63edc1b d55b17e2b4 Author: Justin M. Keyes <justinkz@gmail.com> Date: Wed Jan 15 02:23:44 2025 -0800 Merge #32013 from luukvbaal/shellkind commit 3ee63edc1b0ca6fe664c9d5368aba05ae9a22e9d Merge: 0a7e4e9e5f 575f4bc7d5 Author: Justin M. Keyes <justinkz@gmail.com> Date: Wed Jan 15 02:01:44 2025 -0800 Merge #32001 from MariaSolOs/consistent-namespaces commit 0a7e4e9e5f28f3b6b3c83040430d0a36fcd71fad Author: Andrew Braxton <42975660+andrewbraxton@users.noreply.github.com> Date: Wed Jan 15 04:58:36 2025 -0500 fix(lsp): vim.lsp.enable(...,false) does not disable #32002 Problem: Per the documentation, passing `false` as the `enable` parameter of `vim.lsp.enable()` should disable the given LSP(s), but it does not work due to a logic error. Specifically, `enable == false and nil or {}` will always evaluate to `{}` because `nil` is falsy. Solution: Correct the conditional statement. commit d55b17e2b4e061fd8b330f928785a217c99c9d11 Author: Luuk van Baal <luukvbaal@gmail.com> Date: Tue Jan 14 17:23:11 2025 +0100 fix(messages): verbose kind for nvim_echo() Problem: No "verbose" kind for nvim_echo() opts->verbose. Solution: Pass NULL "kind" to indicate no new kind. commit 5bae80899d9d29d80c129ca92cde75a1583b5efe Author: Luuk van Baal <luukvbaal@gmail.com> Date: Tue Jan 14 12:05:23 2025 +0100 feat(messages): add :!cmd shell message kinds Also print stderr error messages with ErrorMsg highlight group. commit bc69f2723737cfe8916c117483ce32f48ff83544 Author: Christian Clason <c.clason@uni-graz.at> Date: Tue Jan 14 17:18:48 2025 +0100 vim-patch:045564d: runtime(colors): Update colorschemes, include new unokai colorscheme - new unokai colorscheme (similar/inspired by monokai) - the rest: add explicit PopupSelected link to PmenuSel closes: vim/vim#16443 https://github.com/vim/vim/commit/045564d0a73218594691953c0c8bf2035e1e176e Co-authored-by: Maxim Kim <habamax@gmail.com> commit 575f4bc7d5069792188520d1f0e5ed12cc035002 Author: Maria José Solano <majosolano99@gmail.com> Date: Mon Jan 13 19:51:09 2025 -0800 docs: document namespace/augroup convention commit 09e01437c968be4c6e9f6bb3ac8811108c58008c Author: Maria José Solano <majosolano99@gmail.com> Date: Mon Jan 13 19:45:11 2025 -0800 refactor: use nvim.foo.bar format for autocommand groups commit a78eddd54112033eea0212865efd2f75cc59fc93 Author: zeertzjq <zeertzjq@outlook.com> Date: Wed Jan 15 12:05:00 2025 +0800 vim-patch:9.1.1015: Coverity complains about dereferencing NULL value (#32020) Problem: Coverity complains about dereferencing NULL value Solution: Check that cms2 is not null closes: vim/vim#16438 https://github.com/vim/vim/commit/1ac53b84ada3a992f320566737e66fa00d48611f Co-authored-by: Christian Brabandt <cb@256bit.org> commit 850084b519e18122820478a71bb4bfa4c15e528a Author: Maria José Solano <majosolano99@gmail.com> Date: Mon Jan 13 19:39:03 2025 -0800 refactor: use nvim.foo.bar format for namespaces commit 611ef354919f1c6564efd2ff8074545941458ccc Author: Mike <4576770+mike325@users.noreply.github.com> Date: Wed Jan 15 01:39:17 2025 +0100 feat(vim.fs): find(), dir() can "follow" symlinks #31551 Problem: vim.fs.dir(), vim.fs.find() do not follow symlinks. Solution: - Add "follow" flag. - Enable it by default. commit e8a6c1b02122852da83dc52184e78369598d8240 Author: Gregory Anders <greg@gpanders.com> Date: Tue Jan 14 08:19:54 2025 -0600 fix(lsp): schedule call to vim.lsp.start for async root_dir (#31998) When `root_dir` is a function it can (and often will) call the provided callback function in a fast API context (e.g. in the `on_exit` handler of `vim.system`). When the callback function is executed we should ensure that it runs vim.lsp.start on the main event loop. commit f1c45fc7a4a595e460cd245172a5767bddeb09e9 Author: Gregory Anders <greg@gpanders.com> Date: Tue Jan 14 08:18:59 2025 -0600 feat(terminal): support theme update notifications (DEC mode 2031) (#31999) commit 59da82abd91e3be7eb5403c14de012cd149a1c84 Author: bfredl <bjorn.linse@gmail.com> Date: Mon Dec 16 13:31:59 2024 +0100 fix(wininfo): when freeing windows, free the lowest priority wininfo On master (and also before #31539) closing a window could cause the used wininfo for a buffer to change. This is due to always removing the previous NULL wininfo when deleting a window, even if that wininfo had higher priority than the the deleted window's own wininfo. Instead delete the wininfo with lowest priority. This retains the memory saving efect while not affecting the effective value of window options and so on. commit 7eabc8899af8b2fed1472165b74f43965282974f Merge: 25d8c3a5ad 913e81c35f Author: bfredl <bjorn.linse@gmail.com> Date: Tue Jan 14 14:46:34 2025 +0100 Merge pull request #31932 from bfredl/termtab fix(getchar): do not simplify keycodes in terminal mode commit 25d8c3a5ad7e9c5668841e66540ebe34ceda73a7 Author: luukvbaal <luukvbaal@gmail.com> Date: Tue Jan 14 14:02:46 2025 +0100 feat(api): nvim_open_win() relative to tabline and laststatus #32006 Problem: Anchoring a floating window to the tabline and laststatus is cumbersome; requiring autocommands and looping over all windows/tabpages. Solution: Add new "tabline" and "laststatus" options to the `relative` field of nvim_open_win() to place a window relative to. commit e8ddb7a46938f8843abc1c321cfd83cee2ba0020 Author: Christian Clason <c.clason@uni-graz.at> Date: Tue Jan 14 08:32:36 2025 +0100 vim-patch:30377e0: runtime(lyrics): support milliseconds in syntax script The following tool creates LRC files using three fractional digits after the seconds (i.e. milliseconds). References: https://github.com/magic-akari/lrc-maker https://lrc-maker.github.io/ closes: vim/vim#16436 https://github.com/vim/vim/commit/30377e0fe084496911e108cbb33c84cf075e6e33 Co-authored-by: Denilson Sá Maia <denilsonsa@gmail.com> commit 69ad6b12ec473a54f09a11596da724178185eb7a Author: zeertzjq <zeertzjq@outlook.com> Date: Tue Jan 14 18:55:06 2025 +0800 vim-patch:9.1.1010: filetype: VisualCode setting file not recognized (#32003) Problem: filetype: VisualCode setting file not recognized Solution: detect json files in VSCode config directory as jsonc filetype (Konfekt) closes: vim/vim#16400 https://github.com/vim/vim/commit/c200f53cbb03fa11e489a27791d5b9dfc34a6564 Co-authored-by: Konfekt <Konfekt@users.noreply.github.com> commit c5f93d7ab04f93db1470d58ca1f70e947e716c2b Author: Famiu Haque <famiuhaque@proton.me> Date: Sat Dec 28 14:55:22 2024 +0600 refactor(options): remove code for multitype options Problem: It was decided on Matrix chat that multitype options won't be necessary for Neovim options, and that options should only have a single canonical type. Therefore the code for supporting multitype options is unnecessary. Solution: Remove the additional code that's used to provide multitype option support. commit b192d58284a791c55f5ae000250fc948e9098d47 Author: Riley Bruins <ribru17@hotmail.com> Date: Mon Jan 13 09:42:39 2025 -0800 perf(treesitter): calculate folds asynchronously **Problem:** The treesitter `foldexpr` runs synchronous parses to calculate fold levels, which eliminates async parsing performance in the highlighter. **Solution:** Migrate the `foldexpr` to also calculate and apply fold levels asynchronously. commit 5a54681025ec28129c21c875943a3f9c37959f75 Author: Horror Proton <107091537+horror-proton@users.noreply.github.com> Date: Tue Jan 14 00:43:33 2025 +0800 fix(treesitter): uv_dlclose after uv_dlerror commit 0dfa4de9933b548d050feeff5676d580c7103787 Author: Christian Clason <c.clason@uni-graz.at> Date: Tue Jan 14 08:33:11 2025 +0100 build(deps): bump luajit to HEAD - a4f56a459 commit a4f575abd85e734340ee303daace1a63e5ca9782 Author: Xuyuan Pang <xuyuanp@gmail.com> Date: Tue Jan 14 07:17:23 2025 +0800 fix(lsp): minimum height for floating popup #31990 Problem: The floating window for hover and signature help always cuts off a few lines, because the `_make_floating_popup_size` function counts empty lines as having zero height. Solution: Ensure the height is at least 1. commit 34e2185022ab698827b72751d77e218a1b6b6afe Author: Lewis Russell <lewis6991@gmail.com> Date: Fri Jan 10 10:20:43 2025 +0000 fix(options): better handling of empty values Problem: Whether an option is allowed to be empty isn't well defined and isn't properly checked. Solution: - For non-list string options, explicitly check the option value if it is empty. - Annotate non-list string options that can accept an empty value. - Adjust command completion to ignore the empty value. - Render values in Lua meta files commit cb7b4e296238b46025de05203c886d67da401728 Author: luukvbaal <luukvbaal@gmail.com> Date: Mon Jan 13 13:59:34 2025 +0100 feat(messages): "verbose" message kind #31991 commit 47866cd8d20c62afa8a3c3929d3aada2db9162f5 Author: dundargoc <gocdundar@gmail.com> Date: Thu Jan 9 17:28:27 2025 +0100 refactor: delete duplicate utf8-functionality Also remove British National Replacement Character Set. We keep the DEC Special Graphics and ASCII despite it not being unicode as some old software such as calcurse still rely on this functionality. References: - https://github.com/neovim/neovim/pull/31934#discussion_r1911046426 - https://en.wikipedia.org/wiki/DEC_Special_Graphics - https://vt100.net/docs/vt220-rm/chapter2.html#S2.4.3 commit 0631492f9c8044a378dc2a17ea257badfbda6d15 Author: dundargoc <gocdundar@gmail.com> Date: Mon Dec 30 16:01:00 2024 +0100 feat: add vim.fs.relpath This is needed to replace the nvim-lspconfig function is_descendant that some lspconfg configurations still use. commit 913e81c35f162c1e2647565397608f63f38d7043 Author: bfredl <bjorn.linse@gmail.com> Date: Thu Jan 9 14:05:40 2025 +0100 fix(getchar): do not simplify keycodes in terminal mode The code represents a useful pattern in normal mode where remapping `<tab>` will implicitly also remap `<c-i>` unless you remap that explicitly. This relies on the _unmapped_ behavior being identical which is not true in terminal mode, as vterm can distinguish these keys. Vim seems to entangle this with kitty keyboard mode detection which is irrelevant for us. Conditional fallbacks depending on keyboard mode could be done completely inside `vterm/` without getchar.c getting involved, I would think. commit a3ef29d570dd892a1bcbfa80bb242d4aac89a06e Author: Guilherme Soares <48023091+guilhas07@users.noreply.github.com> Date: Mon Jan 13 09:41:49 2025 +0000 test: use temp file #31907 commit 2c16c849986794682a4776ff4ec100d00eeba5ca Author: zeertzjq <zeertzjq@outlook.com> Date: Mon Jan 13 15:18:47 2025 +0800 vim-patch:9.1.1011: popupmenu internal error with some abbr in completion item (#31988) Problem: Popup menu internal error with some abbr in completion item. Solution: Don't compute attributes when there is no corresponding text. Reduce indent in pum_redraw() while at it (zeertzjq). fixes: vim/vim#16427 closes: vim/vim#16435 https://github.com/vim/vim/commit/3a0cc36c69744a7727ce34311d39d2d9d8ddc6f9 commit 99c4bd2f698345fd5706e0ff5d6221b8d3848cfb Merge: f4cff3077b bd4ca22d03 Author: Lewis Russell <lewis6991@gmail.com> Date: Mon Jan 13 06:58:33 2025 +0000 Merge pull request #31631 from ribru17/async_parse_attempt_2 feat(treesitter): async parsing commit f4cff3077b21ba110bc498f3e9331c16d3121cb1 Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 12 19:32:36 2025 +0100 build(deps): bump tree-sitter to v0.24.7 commit bd4ca22d0334a3323313dfd6975a80218ec65e36 Author: Riley Bruins <ribru17@hotmail.com> Date: Fri Dec 20 16:23:52 2024 -0800 feat(treesitter)!: don't parse tree in get_parser() or start() **Problem:** `vim.treesitter.get_parser()` and `vim.treesitter.start()` both parse the tree before returning it. This is problematic because if this is a sync parse, it will stall the editor on large files. If it is an async parse, the functions return stale trees. **Solution:** Remove this parsing side effect and leave it to the user to parse the returned trees, either synchronously or asynchronously. commit 45e606b1fddbfeee8fe28385b5371ca6f2fba71b Author: Riley Bruins <ribru17@hotmail.com> Date: Wed Dec 18 10:48:33 2024 -0800 feat(treesitter): async parsing **Problem:** Parsing can be slow for large files, and it is a blocking operation which can be disruptive and annoying. **Solution:** Provide a function for asynchronous parsing, which accepts a callback to be run after parsing completes. Co-authored-by: Lewis Russell <lewis6991@gmail.com> Co-authored-by: Luuk van Baal <luukvbaal@gmail.com> Co-authored-by: VanaIgr <vanaigranov@gmail.com> commit 3fdc4302415972eb5d98ba832372236be3d22572 Author: Riley Bruins <ribru17@hotmail.com> Date: Sat Jan 11 15:44:07 2025 -0800 perf(treesitter): cache queries strongly **Problem:** Query parsing uses a weak cache which is invalidated frequently **Solution:** Make the cache strong, and invalidate it manually when necessary (that is, when `rtp` is changed or `query.set()` is called) Co-authored-by: Christian Clason <c.clason@uni-graz.at> commit 40bf23adaf98dc357a59f9524a16e06f990faeaa Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 12 12:31:13 2025 +0100 build(deps): bump wasmtime to v25.0.3 commit bf58b757c4c2e1bf2a4afe4279150ca68a68691f Author: Christian Clason <c.clason@uni-graz.at> Date: Sun Jan 12 11:42:02 2025 +0100 vim-patch:9.1.1007: filetype: various ignore are not recognized Problem: filetype: various ignore are not recognized Solution: detect rg/docker/npm/vvsce ignore files as 'gitgnore' filetype (Wu, Zhenyu) Not only prettier, but many programs also support ignore files (like rg, docker, npm, vscode). So use the gitignore filetype for them due to same syntax closes: vim/vim#16428 https://github.com/vim/vim/commit/8cbe2e0a0a78f57bb545a97695bfedd6a95e6992 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu> commit 1a8a48d7e5f8243aff0253a82f4214241eb877d6 Author: zeertzjq <zeertzjq@outlook.com> Date: Sun Jan 12 08:25:57 2025 +0800 vim-patch:9.1.1003: [security]: heap-buffer-overflow with visual mode (#31971) Problem: [security]: heap-buffer-overflow with visual mode when using :all, causing Vim trying to access beyond end-of-line (gandalf) Solution: Reset visual mode on :all, validate position in gchar_pos() and charwise_block_prep() This fixes CVE-2025-22134 Github Advisory: https://github.com/vim/vim/security/advisories/GHSA-5rgf-26wj-48v8 https://github.com/vim/vim/commit/c9a1e257f1630a0866447e53a564f7ff96a80ead Co-authored-by: Christian Brabandt <cb@256bit.org> commit 37316fbac641ecafde29fd750a08ece490d209c1 Author: zeertzjq <zeertzjq@outlook.com> Date: Sun Jan 12 08:04:25 2025 +0800 vim-patch:9.1.1005: completion text is highlighted even with no pattern found (#31973) Problem: completion text is highlighted even with no pattern found Solution: use ins_compl_leader_len() instead of checking compl_leader.length (glepnir) closes: vim/vim#16422 https://github.com/vim/vim/commit/9fddb8ae770be3e16545dd4c2f4cfaad8f62cb40 Co-authored-by: glepnir <glephunter@gmail.com> commit 88dca6a83593a0cf33866addf36cad2e847a2899 Author: zeertzjq <zeertzjq@outlook.com> Date: Sun Jan 12 07:43:58 2025 +0800 vim-patch:partial:9598a63: runtime(doc): add package-<name> helptags for included packages (#31972) Improve how to find the justify package closes: vim/vim#16420 https://github.com/vim/vim/commit/9598a6369bce32d3da831e8968caf4625985ac3c Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Peter Benjamin <petermbenjamin@gmail.com> commit a119aae4d3deebea453ccd7c2dea814aed2c9f21 Author: Gregory Anders <greg@gpanders.com> Date: Sat Jan 11 12:54:43 2025 -0600 feat(diagnostic)!: filter diagnostics by severity before passing to handlers (#30070) BREAKING CHANGE: This changes the list of diagnostics that are passed to a diagnostic handler. If a handler is already filtering by severity itself then this won't break anything, since the handler's filtering will become a no-op. But handlers which depend on receiving the full list of diagnostics may break. Note that diagnostics are only filtered if the handler's configuration has the `severity` option set. If `severity` is not set, the handler still receives the full list of diagnostics. commit 9e0d40f7e45f483e54d38be1266f63240808b4b0 Author: Christian Clason <c.clason@uni-graz.at> Date: Sat Jan 11 10:58:10 2025 +0100 vim-patch:668e9f2: runtime(filetype): don't detect string interpolation as angular fixes: vim/vim#16375 https://github.com/vim/vim/commit/668e9f24037fc7c362ffdf5fc1d5c5b1a8b0e855 Co-authored-by: Christian Brabandt <cb@256bit.org> commit 6a425e7045cca609d95612c0f2cd08d0265238a9 Author: dundargoc <gocdundar@gmail.com> Date: Sun Nov 24 11:29:39 2024 +0100 docs: misc Co-authored-by: Axel <axelhjq@gmail.com> Co-authored-by: Colin Kennedy <colinvfx@gmail.com> Co-authored-by: Daiki Noda <sys9kdr@users.noreply.github.com> Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com> Co-authored-by: Jean-Jacq du Plessis <1030058+jj-du-plessis@users.noreply.github.com> Co-authored-by: Juan Giordana <juangiordana@gmail.com> Co-authored-by: Lincoln Wallace <locnnil0@gmail.com> Co-authored-by: Matti Hellström <hellstrom@scm.com> Co-authored-by: Steven Locorotondo <steven.locorotondo@justeattakeaway.com> Co-authored-by: Yochem van Rosmalen <git@yochem.nl> Co-authored-by: glepnir <glephunter@gmail.com> Co-authored-by: ifish <fishioon@live.com> commit c060a6ea640eb433197ec554ff7cf6469ee1c0e7 Author: zeertzjq <zeertzjq@outlook.com> Date: Sat Jan 11 09:08:01 2025 +0800 vim-patch:9.1.1001: ComplMatchIns highlight hard to read on light background (#31958) Problem: ComplMatchIns highlight hard to read on light background (after v9.1.0996) Solution: define the highlighting group cleared, it should be configured in colorschemes separately (glepnir) closes: vim/vim#16414 https://github.com/vim/vim/commit/ad409876d9cf7e565f99c5e21b9e2e400a83a4d4 Co-authored-by: glepnir <glephunter@gmail.com> commit df45b336f5c097609909dbc9f1e37e88961886d9 Author: zeertzjq <zeertzjq@outlook.com> Date: Sat Jan 11 08:27:50 2025 +0800 vim-patch:695522d: runtime(vim): Update base-syntax, highlight literal string quote escape (#31957) Match the '' escape sequence in literal strings. These were previously ending the current string and starting another concatenated literal string. closes: vim/vim#16415 https://github.com/vim/vim/commit/695522dea3703cf1b4cd4a894ca9a745a0d2756f Co-authored-by: Doug Kearns <dougkearns@gmail.com> commit fbe546e25d21f3184814d696c329d23d146bd615 Author: glepnir <glephunter@gmail.com> Date: Sat Jan 11 07:58:45 2025 +0800 vim-patch:9.1.0996: ComplMatchIns may highlight wrong text (#31931) Problem: ComplMatchIns may highlight wrong text Solution: don't highlight in case of fuzzy match, skip-highlight when not inserting anything (glepnir) closes: vim/vim#16404 https://github.com/vim/vim/commit/e890887b8052561ac5f8dce218e578ed28599cc6 commit dcaf9a60e9c0b3b4f8439897b344b4e632802beb Author: Christian Clason <c.clason@uni-graz.at> Date: Fri Jan 10 20:03:35 2025 +0100 vim-patch:51754c8: runtime(editorconfig): set omnifunc to syntaxcomplete func closes: vim/vim#16419 https://github.com/vim/vim/commit/51754c8a498c39592250a077f56db89dd261995d Co-authored-by: Yochem van Rosmalen <git@yochem.nl> commit aa2b44fbb07f3ab4dd00ea4a3ae7c5d31bc20a9d Author: Guilherme Soares <48023091+guilhas07@users.noreply.github.com> Date: Fri Jan 10 22:46:19 2025 +0000 fix(treesitter): don't return error message on success #31955 Problem: The `vim.treesitter.language.add` function returns a error message even when it succeeds. Solution: Don't return error message on success. commit 37c77ab46baaeadb7c3cc5f3b77bd8ca1d7cd0da Author: luukvbaal <luukvbaal@gmail.com> Date: Fri Jan 10 23:43:45 2025 +0100 fix(messages): attaching/detaching ext_messages causes asserts #31952 Problem: Assert hit related to message kind, which is reset after a ext_messages UI is forcibly detached, so the assertion is expectedly false. Assert hit related to message grid variables after an ext_messages UI attaches while message grid is scrolled. Solution: Don't check message kind assertion if no ext_messages UI is attached. Flush message grid when first/last ext_messages UI attaches/detaches. commit cb02c20569b56545a1657d4f7f8f29171f1037d7 Author: Riley Bruins <ribru17@hotmail.com> Date: Fri Jan 10 12:25:46 2025 -0800 refactor(treesitter.foldexpr): remove unused parse_injections parameter commit 0717dfbfaf36887dab277527eb0a93bf2182297c Author: Justin M. Keyes <justinkz@gmail.com> Date: Fri Jan 10 11:42:04 2025 -0800 refactor(api): deprecate nvim_notify #31938 Problem: The `nvim_notify` API (note: unrelated to `vim.notify()` Lua API) was not given any real motivation in https://github.com/neovim/neovim/pull/13843 There are, and were, idiomatic and ergonomic alternatives already. Solution: Deprecate `nvim_notify`. commit b06f42b5023b2eec576e5bf22cdacd4c1ee4a939 Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 10 17:17:34 2025 +0800 vim-patch:df4a7d7: runtime(tiasm): use correct syntax name tiasm in syntax script (#31942) vim-patch:df4a7d7: runtime(tiasm): use correct syntax name tiasm in syntax script closes: vim/vim#16416 https://github.com/vim/vim/commit/df4a7d761740d59a4f911c9e13ac620a459cdea6 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu> commit 87610d82db912cda8877198c25dabbf2bb08f0aa Author: Luuk van Baal <luukvbaal@gmail.com> Date: Thu Jan 9 17:58:37 2025 +0100 fix(decor): set invalid flag for end of invalidated paired marks commit a37784ad831fdf31e7eeafdd41f7d3cb81b1a07f Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 10 08:04:02 2025 +0800 vim-patch:9.1.1000: tests: ruby tests fail with Ruby 3.4 (#31940) Problem: tests: ruby tests fail with Ruby 3.4 Solution: adjust expected output for Ruby 3.4 (Yee Cheng Chin) Vim's Ruby tests relied on explicit matching of output texts which are fragile in design. Ruby 3.4 has changed the output slightly (using 'name' instead of `name', and also using more spaces in dictionary printouts). Modify the Vim tests to be less fragile to such changes. closes: vim/vim#16411 https://github.com/vim/vim/commit/ebea31e454b9a1731cde845226f2c28ca5c097b1 Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com> commit 846a2019c0e3b3a91477c12ec2c4ac85861b4d67 Author: zeertzjq <zeertzjq@outlook.com> Date: Fri Jan 10 08:03:44 2025 +0800 vim-patch:9.1.0999: Vim9: leaking finished exception (#31939) Problem: leaking finished exception (after v9.1.0984) Solution: use finish_exception to clean up caught exceptions (Yee Cheng Chin) In Vimscript, v:exception/throwpoint/stacktrace are supposed to reflect the currently caught exception, and be popped after the exception is finished (via endtry, finally, or a thrown exception inside catch). Vim9script does not handle this properly, and leaks them instead. This is clearly visible when launching GVim with menu enabled. A caught exception inside the s:BMShow() in menu.vim would show up when querying `v:stacktrace` even though the exception was already caught and handled. To fix this, just use the same functionality as Vimscript by calling `finish_exception` to properly restore the states. Note that this assumes `current_exception` is always the same as `caught_stack` which believe should be the case. Added tests for this. Also fix up test_stacktrace to properly test the stack restore behavior where we have nested exceptions in catch blocks and to also test the vim9script functionality properly. - Also, remove its dependency on explicitly checking a line number in runtest.vim which is a very fragile way to write tests as any minor change in runtest.vim (shared among all tests) would require changing test_stacktrace.vim. We don't actually need such granularity in the test. closes: vim/vim#16413 https://github.com/vim/vim/commit/2051af1642843426714efc2572c3e270fe0948be Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com> commit 7c00e0efbb18e8627ac59eaadf564a9f1b2bafcd Author: Justin M. Keyes <justinkz@gmail.com> Date: Thu Jan 9 09:26:45 2025 -0800 docs: misc #31867 commit 0c296ab22484b4c009d119908d1614a6c6d96b2c Author: Riley Bruins <ribr…

justinmk mentioned this pull request Jan 5, 2025

vim.o.term is missing #31860

Open

justinmk force-pushed the doc2 branch 5 times, most recently from edc4fb5 to 4fc5fb9 Compare January 9, 2025 17:08

justinmk marked this pull request as ready for review January 9, 2025 17:09

docs: misc

e5031fe

justinmk force-pushed the doc2 branch from 4fc5fb9 to e5031fe Compare January 9, 2025 17:17

justinmk merged commit 7c00e0e into neovim:master Jan 9, 2025
34 of 36 checks passed

justinmk deleted the doc2 branch January 9, 2025 17:26

AbhijithKumble pushed a commit to AbhijithKumble/neovim that referenced this pull request Jan 11, 2025

docs: misc neovim#31867

e373a68

mrowegawd pushed a commit to mrowegawd/neovim that referenced this pull request Jan 30, 2025

docs: misc neovim#31867

b600369

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs: misc #31867

docs: misc #31867

justinmk commented Jan 5, 2025

docs: misc #31867

docs: misc #31867

Conversation

justinmk commented Jan 5, 2025