aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
...
* vim-patch:9.1.0292: filetype: XDG mimeapps.list file is not recognizedzeertzjq2024-04-12
| | | | | | | | | | | | | | Problem: filetype: XDG mimeapps.list file is not recognized Solution: Detect mimeapps.list as dosini filetype (Wu, Zhenyu) Refer: https://wiki.archlinux.org/title/XDG_MIME_Applications#Format closes: vim/vim#14451 https://github.com/vim/vim/commit/efd752ec384980135c36b9fb673574e64c270c90 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0291: filetype: libreoffice config files are not recognizedzeertzjq2024-04-12
| | | | | | | | | | | | Problem: filetype: libreoffice config files are not recognized Solution: Detect Libreoffice config fils as xml/dosini (Wu, Zhenyu) closes: vim/vim#14453 https://github.com/vim/vim/commit/73c89bcf79df280b8698f77374afabd9494dc741 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0304: filetype: cgdb config file is not recognized (#28294)zeertzjq2024-04-12
| | | | | | | | | | | Problem: filetype: cgdb config file is not recognized Solution: Detect cgdbrc files as cgdbrc filetype (Wu, Zhenyu) closes: vim/vim#14458 https://github.com/vim/vim/commit/1492fe69037586b6c625d42205d77dd38ba51640 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0303: filetype: some protocol buffer files not recognized (#28293)zeertzjq2024-04-12
| | | | | | | | | | | | | Problem: filetype: some protocol buffer files not recognized Solution: Detect '*.textproto', '*.textpb', '*.txtpb' as pbtxt files (Bruno Belanyi) See: https://protobuf.dev/reference/protobuf/textformat-spec/#text-format-files closes: vim/vim#14463 https://github.com/vim/vim/commit/e54a8e7c73bbfba0c77e928f27fb3a9bffd2e8fd Co-authored-by: Bruno BELANYI <bruno@belanyi.fr>
* vim-patch:9.1.0302: filetype: blueprint files are not recognized (#28292)zeertzjq2024-04-12
| | | | | | | | | | | | | Problem: filetype: blueprint files are not recognized Solution: Detect '*.bp' files as blueprint files, add a minimal filetype plugin (Bruno Belanyi) See: https://source.android.com/docs/setup/build closes: vim/vim#14488 https://github.com/vim/vim/commit/6be7ef5bc734ce6045d6f919f1a8559a3fa7f2fd Co-authored-by: Bruno BELANYI <bruno@belanyi.fr>
* vim-patch:9.1.0290: filetype: xilinx files are not recognized (#28295)zeertzjq2024-04-12
| | | | | | | | | | | | Problem: filetype: xilinx files are not recognized Solution: Add a few xilinx specific file patterns, inspect lpr files for being xml/pascal (Wu, Zhenyu) closes: vim/vim#14454 https://github.com/vim/vim/commit/614691ceefb2b2470cd9097013ffc140f81d6a71 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0289: filetype: some TeX files are not recognized (#28291)zeertzjq2024-04-12
| | | | | | | | | | | | Problem: filetype: some TeX files are not recognized Solution: Add more patterns for TeX files and inspect a few more files for being TeX files (Wu, Zhenyu) closes: vim/vim#14456 https://github.com/vim/vim/commit/61ee833a504ae73bc6b3e2527a81582263f02afd Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:83424105cb42 (#28298)zeertzjq2024-04-12
| | | | | | | | | runtime(doc): mention :argded for :argedit related: vim/vim#14464 https://github.com/vim/vim/commit/83424105cb4219fe4280aa86df5173096186bba2 Co-authored-by: Christian Brabandt <cb@256bit.org>
* test: macros in Visual mode without default mappings (#28288)zeertzjq2024-04-12
|
* vim-patch:fcbefe74f161 (#28285)zeertzjq2024-04-12
| | | | | | | | | | | runtime(compiler): add vimdoc closes: vim/vim#14459 https://github.com/google/vimdoc generates vim help files from vimscript files https://github.com/vim/vim/commit/fcbefe74f1619dfd925033d83a6d233c686409d4 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:3cb2b3776700 (#28283)zeertzjq2024-04-12
| | | | | | | | | runtime(doc): clarify behaviour or :argadd and :argedit related: vim/vim#14464 https://github.com/vim/vim/commit/3cb2b3776700988e0c9d4ea37d0b05e371e2bbfd Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:dbca7d80457dzeertzjq2024-04-11
| | | | | | | | | | | | ftplugin(asm): add Matchit support closes: vim/vim#14461 Refer https://github.com/vim/vim/blob/master/runtime/ftplugin/masm.vim#L18-L29 https://github.com/vim/vim/commit/dbca7d80457d026f6d6a5cc7e916b94df0ca6e03 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:27f17a6d3493zeertzjq2024-04-11
| | | | | | | | | | runtime(asm): add basic indent support closes: vim/vim#14383 https://github.com/vim/vim/commit/27f17a6d3493f611f5bdc376217535f9c49b479b Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:556c62165963zeertzjq2024-04-11
| | | | | | | | | | ftplugin(gdb): add matchit support closes: vim/vim#14462 https://github.com/vim/vim/commit/556c62165963359f1b35f17a49913fc61c43f937 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:6ce07edd600e (#28275)zeertzjq2024-04-11
| | | | | | | | | runtime(compiler): fix inaccuracies in pandoc compiler (vim/vim#14467) as kindly pointed out by @Freed-Wu https://github.com/vim/vim/commit/6ce07edd600e73e5aaebeafead6e82b41bd00e12 Co-authored-by: Enno <Konfekt@users.noreply.github.com>
* vim-patch:04e5363b8238 (#28268)zeertzjq2024-04-11
| | | | | | | | | | | | | | | | | | runtime(vim): Improve Vim9 and legacy-script comment highlighting (vim/vim#13104) This is a first-pass attempt to limit matching of Vim9 and legacy-script comments to the appropriate syntactic contexts. Vim9-script comments are highlighted at top level in a Vim9-script file, in all :def functions, and in all :autocmd and :commmand command blocks. Legacy-script comments are highlighted at top level in a legacy script file, in all :func functions and in the Vim9-script preamble before the :vim9script marker command. Fixes vim/vim#13047, vim/vim#11307 and vim/vim#9587. https://github.com/vim/vim/commit/04e5363b823827f144409df011376d00ea6df750 Co-authored-by: dkearns <dougkearns@gmail.com>
* vim-patch:9.1.0297: Patch 9.1.0296 causes too many issues (#28263)zeertzjq2024-04-11
| | | | | | | | | | | | | | | | | Problem: Patch 9.1.0296 causes too many issues (Tony Mechelynck, chdiza, CI) Solution: Back out the change for now Revert "patch 9.1.0296: regexp: engines do not handle case-folding well" This reverts commit 7a27c108e0509f3255ebdcb6558e896c223e4d23 it causes issues with syntax highlighting and breaks the FreeBSD and MacOS CI. It needs more work. fixes: vim/vim#14487 https://github.com/vim/vim/commit/c97f4d61cde24030f2f7d2318e1b409a0ccc3e43 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:c9ec20d94ea5 (#28267)zeertzjq2024-04-11
| | | | | | | | | | | | | runtime(doc): Update documentation - Add security e-mail for private bugreports - Remove mentioning of the voting feature closes: vim/vim#14483 https://github.com/vim/vim/commit/c9ec20d94ea5c1ea263e70503e82abcdd27d3463 Co-authored-by: RestorerZ <restorer@mail2k.ru> Co-authored-by: Christian Brabandt <cb@256bit.org>
* fix(treesitter): use tree range instead of tree root node rangealtermo2024-04-10
|
* fix(lsp): prevent code-lens refresh from becoming a permanent no-op (#28228)Yi Ming2024-04-10
| | | | | | To avoid repeatedly requesting a buffer multiple times before a request is completed, the current implementation puts the requested buffer into the active_refreshes table before requesting. But since we only remove the buffer from active_refreshes in the lsp-handler of textDocument/codeLens, this will cause if the user sends a request that cannot trigger lsp-handler (for example, if there is an LSP server attached to the current buffer, and especially when the user creates an autocmd which performs vim.lsp.codelens.refresh after the BufEnter event is triggered like in the document example), this buffer will be put into active_refreshes, and there is no way to remove it, which will result in all subsequent vim.lsp.codelens.refresh not requesting textDocument/codeLens.
* fix(lsp): empty commands should not be considered executable (#28216)Yi Ming2024-04-10
| | | According to the LSP specification, the CodeLens.command is optional but the CodeLens.command.command is not optional, which means the correct representation of a display-only code lens is indeed one with a command with a title to display and an empty string as command.
* vim-patch:9.1.0296: regexp: engines do not handle case-folding well (#28259)zeertzjq2024-04-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Regex engines do not handle case-folding well Solution: Correctly calculate byte length of characters to skip When the regexp engine compares two utf-8 codepoints case insensitively it may match an adjacent character, because it assumes it can step over as many bytes as the pattern contains. This however is not necessarily true because of case-folding, a multi-byte UTF-8 character can be considered equal to some single-byte value. Let's consider the pattern 'ſ' and the string 's'. When comparing and ignoring case, the single character 's' matches, and since it matches Vim will try to step over the match (by the amount of bytes of the pattern), assuming that since it matches, the length of both strings is the same. However in that case, it should only step over the single byte value 's' so by 1 byte and try to start matching after it again. So for the backtracking engine we need to ensure: - we try to match the correct length for the pattern and the text - in case of a match, we step over it correctly The same thing can happen for the NFA engine, when skipping to the next character to test for a match. We are skipping over the regstart pointer, however we do not consider the case that because of case-folding we may need to adjust the number of bytes to skip over. So this needs to be adjusted in find_match_text() as well. A related issue turned out, when prog->match_text is actually empty. In that case we should try to find the next match and skip this condition. fixes: vim/vim#14294 closes: vim/vim#14433 https://github.com/vim/vim/commit/7a27c108e0509f3255ebdcb6558e896c223e4d23 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:e43ace558aee (#28258)zeertzjq2024-04-10
| | | | | | | | | | runtime(vim): Update base-syntax, no curly-brace names in Vim9 script (vim/vim#14466) Remove curly-brace name matching for :def functions. This is not supported in Vim9 script. https://github.com/vim/vim/commit/e43ace558aee904f5ebb805daed763961bdbccde Co-authored-by: dkearns <dougkearns@gmail.com>
* vim-patch:9.1.0283: Several small issues in doc and tests (#28249)zeertzjq2024-04-09
| | | | | | | | | | | | Problem: Wrong doc style for pandoc syntax description, Test_diff_eob_halfpage() may fail depending on screen size, using braces in highlight.c when not necessary Solution: Fix pandoc documentation, make sure the window for the test has 7 lines, remove the braces. https://github.com/vim/vim/commit/a040019be68859f0667ae475de8d67bb755596ed Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0276: No pandoc syntax supportChristian Clason2024-04-09
| | | | | | | | | | | | | Problem: No pandoc syntax support Solution: Add pandoc syntax and compiler plugins (Wu, Zhenyu, Konfekt) closes: vim/vim#14389 https://github.com/vim/vim/commit/7005b7ee7f282b24378c2a844366cb8616cad5d7 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu> Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* vim-patch:a2385c233499Christian Clason2024-04-09
| | | | | | | | | | runtime(cuda): Update cuda keywords, remove uncommonly used enumeration constants closes: vim/vim#14406 https://github.com/vim/vim/commit/a2385c23349935d4bd6780a538f3a8f46a29d952 Co-authored-by: jiangyinzuo <jiangyinzuo@foxmail.com>
* vim-patch:9.1.0278: filetype: zathurarc files not recognizedChristian Clason2024-04-09
| | | | | | | | | | | | Problem: filetype: zathurarc files not recognized Solution: Detect '.zathurarc' files as zathurarc filetype, add zathurarc filetype (Wu, Zhenyu) closes: vim/vim#14380 https://github.com/vim/vim/commit/72d81a66edd835aeff3f539ccd0f97afb1ebd63c Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0275: filetype: R history files are not recognizedChristian Clason2024-04-09
| | | | | | | | | | | | Problem: filetype: R history files are not recognized Solution: Detect '.Rhistory' files as r filetype (Wu, Zhenyu) closes: vim/vim#14440 https://github.com/vim/vim/commit/fc21b6437ce91368c2d53437177083b8bc375720 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0279: filetype: roc files are not recognizedChristian Clason2024-04-09
| | | | | | | | | | | | Problem: filetype: roc files are not recognized Solution: Detect '*.roc' files as roc filetype, add a basic filetype plugin (nat-418) closes: vim/vim#14416 https://github.com/vim/vim/commit/196b6678c5483217ea5bc7d047b02c915615dae6 Co-authored-by: nat-418 <93013864+nat-418@users.noreply.github.com>
* vim-patch:9.1.0277: Cannot highlight the Command-line (#28244)zeertzjq2024-04-09
| | | | | | | | | | | | | Problem: Cannot highlight the Command-line Solution: Add the MsgArea highlighting group (Shougo Matsushita) closes: vim/vim#14327 https://github.com/vim/vim/commit/be2b03c6eecea3eae5d460e3c19ee43b73b29928 Cherry-pick Test_highlight_User() from patch 8.2.1077. Co-authored-by: Shougo Matsushita <Shougo.Matsu@gmail.com>
* test: improve test conventionsdundargoc2024-04-08
| | | | Work on https://github.com/neovim/neovim/issues/27004.
* vim-patch:9.1.0273: filetype: keymap files are not recognizedChristian Clason2024-04-08
| | | | | | | | | | | | Problem: filetype: keymap files are not recognized Solution: Detect '*.keymap' files as Device Tree Files (0xadk) closes: vim/vim#14434 https://github.com/vim/vim/commit/b78753db5fac879a76da3519101e815451d0d455 Co-authored-by: 0xadk <0xadk@users.noreply.github.com>
* vim-patch:9cd9e759ab1e (#28224)zeertzjq2024-04-08
| | | | | | | | | | | | runtime(doc): Normalise builtin-function optional parameter formatting These should generally be formatted as func([{arg}]) and referenced as {arg} in the description. closes: vim/vim#14438 https://github.com/vim/vim/commit/9cd9e759ab1e6e6adb24a23648eed41e4d94d522 Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* fix(health): check unmatching python_glob as empty table (#28215)Barrett Ruth2024-04-07
|
* refactor: remove fn_booldundargoc2024-04-06
| | | | | It's better to use vim.fn directly instead of creating minor abstractions like fn_bool.
* vim-patch:9.1.0266: filetype: earthfile files are not recognized (#28207)zeertzjq2024-04-06
| | | | | | | | | | | Problem: filetype: earthfile files are not recognized Solution: Detect 'Earthfile' as earthfile (Gaëtan Lehmann) closes: vim/vim#14408 https://github.com/vim/vim/commit/28e5e7c48483254604506dbce5eb61396ff65808 Co-authored-by: Gaëtan Lehmann <gaetan.lehmann@gmail.com>
* docs: don't mention executable() can return -1dundargoc2024-04-06
| | | | This cannot happen for neovim.
* docs: tags for commenting mappings without "-default" suffix (#28205)zeertzjq2024-04-06
| | | | | | | | This actually won't cause "duplicate tag" errors if plugins have tags of the same name, because E154 is only given for duplicate tags in the same directory. Without those tags, trying to use :h for these mappings jumps to other places, because there are matches with higher score.
* vim-patch:cec44eae82c1 (#28199)Yinzuo Jiang2024-04-06
| | | | | | | runtime: Remove more fallback :CompilerSet definitions from compiler plugins Continue with vim/vim#14399 vim/vim@cec44ea
* vim-patch:b73faa1c02d0 (#28193)zeertzjq2024-04-06
| | | | | | | | | | runtime: fix :compiler leaving behind a g:makeprg variable (vim/vim#14414) Problem: :compiler may leave behind a g:makeprg variable after vim/vim#14336. Solution: Use a script local variable. https://github.com/vim/vim/commit/b73faa1c02d0911a60bddd1ba343cf620f2cd124 Also apply previously omitted change to compiler/context.vim.
* fix(treesitter): update parsers and queriesChristian Clason2024-04-05
|
* feat(comment): add built-in commentingEvgeni Chasnovski2024-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Design - Enable commenting support only through `gc` mappings for simplicity. No ability to configure, no Lua module, no user commands. Yet. - Overall implementation is a simplified version of 'mini.comment' module of 'echasnovski/mini.nvim' adapted to be a better suit for core. It basically means reducing code paths which use only specific fixed set of plugin config. All used options are default except `pad_comment_parts = false`. This means that 'commentstring' option is used as is without forcing single space inner padding. As 'tpope/vim-commentary' was considered for inclusion earlier, here is a quick summary of how this commit differs from it: - **User-facing features**. Both implement similar user-facing mappings. This commit does not include `gcu` which is essentially a `gcgc`. There are no commands, events, or configuration in this commit. - **Size**. Both have reasonably comparable number of lines of code, while this commit has more comments in tricky areas. - **Maintainability**. This commit has (purely subjectively) better readability, tests, and Lua types. - **Configurability**. This commit has no user configuration, while 'vim-commentary' has some (partially as a counter-measure to possibly modifying 'commentstring' option). - **Extra features**: - This commit supports tree-sitter by computing `'commentstring'` option under cursor, which can matter in presence of tree-sitter injected languages. - This commit comments blank lines while 'tpope/vim-commentary' does not. At the same time, blank lines are not taken into account when deciding the toggle action. - This commit has much better speed on larger chunks of lines (like above 1000). This is thanks to using `nvim_buf_set_lines()` to set all new lines at once, and not with `vim.fn.setline()`.
* vim-patch:408281e16a36Christian Clason2024-04-05
| | | | | | | | | | | | | | | runtime: Remove fallback :CompilerSet definition from compiler plugins The :CompilerSet command was added in version Vim 6.4 which was released twenty years ago. Other runtime files do not support versions of that vintage so it is reasonable to remove this fallback command definition now. closes: vim/vim#14399 https://github.com/vim/vim/commit/408281e16a36c15eed10fbf0406fa8ab159fc4bf Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* feat(lsp): set workDoneToken in initialize request (#28182)Mathias Fußenegger2024-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Some servers don't report progress during initialize unless the client sets the `workDoneToken` See https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#initiatingWorkDoneProgress In particular: > There is no specific client capability signaling whether a client will > send a progress token per request. The reason for this is that this is > in many clients not a static aspect and might even change for every > request instance for the same request type. So the capability is signal > on every request instance by the presence of a workDoneToken property. And: > Servers can also initiate progress reporting using the > window/workDoneProgress/create request. This is useful if the server > needs to report progress outside of a request (for example the server > needs to re-index a database). The token can then be used to report > progress using the same notifications used as for client initiated > progress. So far progress report functionality was relying entirely on the latter. Solution: Set a `workDoneToken` Closes https://github.com/neovim/neovim/issues/27938
* feat(defaults): add :Inspect to right-click menu (#28181)zeertzjq2024-04-05
| | | | | | | Ref #21393 - Move default user commands to _defaults.lua as that now contains all kinds of defaults rather than just default mappings and menus. - Remove the :aunmenu as there are no menus when _defaults.lua is run.
* vim-patch:8.1.0815: dialog for file changed outside of Vim not tested (#28184)zeertzjq2024-04-05
| | | | | | | | | Problem: Dialog for file changed outside of Vim not tested. Solution: Add a test. Move FileChangedShell test. Add 'L' flag to feedkeys(). https://github.com/vim/vim/commit/5e66b42aae7c67a3ef67617d4bd43052ac2b73ce Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:5ccdcc482e29Christian Clason2024-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(java): Improve the matching of contextual keywords - Recognise a _record_ contextual keyword. - Recognise _non-sealed_, _sealed_, and _permits_ contextual keywords. - Admit _$_ to keyword characters. - Group _abstract_, _final_, _default_, _(non-)sealed_ (apart from _(non-)sealed_, the incompossibility of these modifiers calls for attention). - Remove another _synchronized_ keyword redefinition. I have also replaced a function with an expression. Before patch 8.1.0515, it should have been declared :function! to work with repeatable script sourcing; there is less to worry about with an expression. References: https://openjdk.org/jeps/395 (Records) https://openjdk.org/jeps/409 (Sealed Classes) https://docs.oracle.com/javase/specs/jls/se21/html/jls-3.html#jls-3.8 closes: vim/vim#14403 https://github.com/vim/vim/commit/5ccdcc482e299609ae8852a75b22190e38b9b5df Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com>
* vim-patch:08d2401fbc6dChristian Clason2024-04-04
| | | | | | | | | | runtime(netrw): filetype not detected when editing remote files fixes: vim/vim#14400 https://github.com/vim/vim/commit/08d2401fbc6de2606aca69add401e2ffca772aa2 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:89cc03af71d9 (#28168)zeertzjq2024-04-04
| | | | | | | runtime(doc): sort filetype.txt in the alphabetical order (vim/vim#14395) https://github.com/vim/vim/commit/89cc03af71d9beb839d296b78a87869e7a0a8996 Co-authored-by: K.Takata <kentkt@csc.jp>
* vim-patch:9.1.0253: filetype: typespec files are not recognizedChristian Clason2024-04-03
| | | | | | | | | | | | | | Problem: filetype: typespec files are not recognized Solution: Detect '*.tsp' files as typespec (Hilmar Wiegand) Specs is at https://typespec.io/ closes: vim/vim#14392 https://github.com/vim/vim/commit/6c9f4f98f1cda3793406724a260cd651210a5d0d Co-authored-by: Hilmar Wiegand <me@hwgnd.de>
generated by cgit (git 2.34.1) at 2025-06-30 00:20:10 +0000