aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* vim-patch:4ba70cab37d2 (#28338)zeertzjq2024-04-15
| | | | | | | | | | | | runtime(vim): Update base-syntax, fix nested function folding (vim/vim#14397) Only match function folding start and end patterns at the start of a line, excluding heredocs and :append/:change/:insert commands. Fixes vim/vim#14393 https://github.com/vim/vim/commit/4ba70cab37d2a625d8c59bb136070ef9d1976934 Co-authored-by: dkearns <dougkearns@gmail.com>
* vim-patch:e92ed1b45c54 (#28337)zeertzjq2024-04-15
| | | | | | | runtime(vim): don't set compiler, update a comment for vimdoc compiler (vim/vim#14532) https://github.com/vim/vim/commit/e92ed1b45c5432235b0541521124d965b9d6a9a2 Co-authored-by: Shane-XB-Qian <shane.qian@foxmail.com>
* vim-patch:9.1.0329: String interpolation fails for Dict type (#28335)zeertzjq2024-04-15
| | | | | | | | | | | | | Problem: String interpolation fails for Dict type Solution: Support Dict data type properly, also support :put =Dict (without having to convert it to string() first) (Yegappan Lakshmanan) fixes: vim/vim#14529 closes: vim/vim#14541 https://github.com/vim/vim/commit/f01493c55062c01b1cdf9b1e946577f4d1bdddf3 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* feat(api)!: nvim_open_win: noautocmd blocks all autocmds #28192Sean Dewar2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | Problem: noautocmd is confusing; despite its name, it doesn't block all autocommands (instead it blocks only those related to setting the buffer), and is commonly used by plugins to open windows while producing minimal side-effects. Solution: be consistent and block all autocommands when noautocmd is set. This includes WinNew (again), plus autocommands from entering the window (if enter is set) like WinEnter, WinLeave, TabEnter, .etc. See the discussion at https://github.com/neovim/neovim/pull/14659#issuecomment-2040029517 for more information. Remove win_set_buf's noautocmd argument, as it's no longer needed. NOTE: pum_create_float_preview sets noautocmd for win_set_buf, but all its callers already use block_autocmds. Despite that, pum_create_float_preview doesn't actually properly handle autocommands (it has no checks for whether those from win_enter or nvim_create_buf free the window). For now, ensure autocommands are blocked within it for correctness (in case it's ever called outside of a block_autocmds context; the function seems to have been refactored in #26739 anyway).
* fix(defaults): only repeat macro for each selected line if linewise (#28289)zeertzjq2024-04-15
| | | | | | As mentioned in #28287, repeating a macro for each selected line doesn't really make sense in non-linewise Visual mode. Fix #28287
* vim-patch:9.1.0318: filetype: translate shell config files are not recognizedChristian Clason2024-04-14
| | | | | | | | | | | | | | Problem: filetype: translate shell config files are not recognized Solution: Detect 'init.trans', 'translate-shell' and '.trans' files as clojure (Wu, Zhenyu) See: https://github.com/soimort/translate-shell/wiki/Configuration closes: vim/vim#14499 https://github.com/vim/vim/commit/4b5cd7257ee99384940d5210cf50298ff925924e Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0317: filetype: matplotlibrc files are not recognizedChristian Clason2024-04-14
| | | | | | | | | | | | | | Problem: filetype: matplotlibrc files are not recognized Solution: Detect 'matplotlibrc' file as yaml filetype (Wu, Zhenyu) See: https://matplotlib.org/stable/users/explain/customizing.html#the-matplotlibrc-file closes: vim/vim#14501 https://github.com/vim/vim/commit/55d4f3c006689945599589a90036923b1752754f Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0316: filetype: some sh and confini files not recognizedChristian Clason2024-04-14
| | | | | | | | | | | | | | | | | Problem: filetype: some sh and confini files not recognized Solution: Detect neofetch, '.xprofile', XDG-User-Dirs files, paru and makepkg config files (Wu, Zhenyu) See: - https://github.com/dylanaraps/neofetch/wiki/Customizing-Info#config-file-location - https://www.freedesktop.org/wiki/Software/xdg-user-dirs/ closes: vim/vim#14505 https://github.com/vim/vim/commit/5a9f7e6750727f81d0638e7ce0ee6bcb01742570 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0315: filetype: a few more dosini files are not recognizedChristian Clason2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | Problem: filetype: a few more dosini files are not recognized Solution: Detect wakatime, reply config files, flatpak, nfs config files and a few more python tools as dosini (or toml) (Wu, Zhenyu) Refer: - https://packaging.python.org/en/latest/specifications/pypirc/ - https://jorisroovers.com/gitlint/latest/configuration/ - https://pylint.pycqa.org/en/latest/user_guide/usage/run.html#command-line-options - https://docs.bpython-interpreter.org/en/latest/configuration.html - https://mypy.readthedocs.io/en/stable/config_file.html#the-mypy-configuration-file - https://black.readthedocs.io/en/stable/usage_and_configuration/the_basics.html#configuration-via-a-file - https://github.com/wakatime/wakatime-cli?tab=readme-ov-file#usage - https://metacpan.org/dist/Reply/view/bin/reply#-cfg-~/.replyrc close: vim/vim#14512 https://github.com/vim/vim/commit/0881329d129866fa49444e7fb6e622e54285a8ff Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:ce06493aeb3d (#28321)zeertzjq2024-04-14
| | | | | | | | | | | | | runtime(vim): Update base-syntax, add legacy header folding Allow for syntax-based folding of Vim9 script legacy header regions. This is enabled with the "H" flag of the g:vimsyn_folding config variable. closes: vim/vim#14530 https://github.com/vim/vim/commit/ce06493aeb3d198d13de289ac39d1ed0f1604429 Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* vim-patch:5392970921abChristian Clason2024-04-13
| | | | | | | | | | | runtime(i3config): Line continuation is not detected for 'set' command (vim/vim#14531) Problem: Valid i3config syntax is highlighted as error. Solution: Skip over line-breaks correctly. https://github.com/vim/vim/commit/5392970921aba5112f529a5d93407ae65c285fb1 Co-authored-by: julio-b <julio.bacel@gmail.com>
* vim-patch:122d06858568Christian Clason2024-04-13
| | | | | | | | runtime(go): fix highlighting import string followed by some comment (vim/vim#14538) https://github.com/vim/vim/commit/122d068585686babd63f0b729759ec269171d464 Co-authored-by: Linda_pp <rhysd@users.noreply.github.com>
* fix(defaults): auto-close terminal for &shell with args (#28276)Jaehwang Jung2024-04-13
| | | | | | | | | Problem: The `:terminal` auto-close logic does not support `&shell` that has arguments, e.g., `/bin/bash -O globstar`. Solution: Join `argv` and match `&shell`. This is not perfect since `&shell` may contain irregular spaces and quotes, but it seems to be good enough.
* vim-patch:0549c503ba20zeertzjq2024-04-13
| | | | | | | | runtime(dts): include ftplugin support (vim/vim#14522) https://github.com/vim/vim/commit/0549c503ba20345097a14122f0a18dde69d470c5 Co-authored-by: wzy <32936898+Freed-Wu@users.noreply.github.com>
* vim-patch:159dc0fcf950zeertzjq2024-04-13
| | | | | | | | | | runtime(kconfig): add include to ftplugin (vim/vim#14524) related: vim/vim#14521 https://github.com/vim/vim/commit/159dc0fcf950e6c21f97cc337bcf19ff90ce73c6 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0311: filetype: Some config files are not recognized (#28311)zeertzjq2024-04-13
| | | | | | | | | | | | | | | Problem: Some config files are not recognized Solution: Add some patterns for chktex, ripgreprc and ctags config files. See: https://www.nongnu.org/chktex/ See: https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#configuration-file See: https://docs.ctags.io/en/latest/option-file.html#order-of-loading-option-files closes: vim/vim#14506 https://github.com/vim/vim/commit/a1dcd76ce791b5b8bd093765a99b71aa163300a5 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* revert: "feat(health): fold successful healthchecks #22866"dundargoc2024-04-13
| | | | | | | | | This reverts commit 4382d2ed564b80944345785d780cf1b19fb23ba8. The story for this feature was left in an incomplete state. It was never the intention to unilaterally fold all information, only the ones that did not contain relevant information. This feature does more harm than good in its incomplete state.
* vim-patch:9.1.0305: filetype: some history files are not recognized (#28300)zeertzjq2024-04-12
| | | | | | | | | | | Problem: filetype: some history files are not recognized Solution: Add some history patterns to filetype.vim (Wu, Zhenyu) closes: vim/vim#14513 https://github.com/vim/vim/commit/da70feabeab77581e48a7ca9c8d5f950c1c2814e Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0307: filetype: texdoc config files is not recognizedzeertzjq2024-04-12
| | | | | | | | | | | | | | Problem: filetype: texdoc config files is not recognized Solution: Detect 'texdoc.cnf' as conf filetype (Wu, Zhenyu) See: https://github.com/TeX-Live/texdoc/blob/master/texdoc.cnf closes: vim/vim#14507 https://github.com/vim/vim/commit/7fdbd1bb58192650bec067a0f224c1fa971c6782 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0306: filetype: x11vnc config file is not recognizedzeertzjq2024-04-12
| | | | | | | | | | | | | | Problem: filetype: x11vnc config file is not recognized Solution: Detect '.x11vncrc' as conf filetype (Wu, Zhenyu) See: https://linux.die.net/man/1/x11vnc closes: vim/vim#14511 https://github.com/vim/vim/commit/58ce78ad438deefec54fd6206166ca2794cd6efe Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0295: filetype: pip config files are not recognizedzeertzjq2024-04-12
| | | | | | | | | | | | Problem: filetype: pip config files are not recognized Solution: detect pip.conf as dosini filetype (Wu, Zhenyu) closes: vim/vim#14448 https://github.com/vim/vim/commit/d2b95b8446233e0021a8c0cd672f8fae748e3955 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0293: filetype: lxqt config files are not recognizedzeertzjq2024-04-12
| | | | | | | | | | | | | Problem: filetype: lxqt config files are not recognized Solution: Detect {lxqt,screengrab}/*.conf files as dosini, fix failing filetype test for */tex/latex/**.cfg (Wu, Zhenyu) closes: vim/vim#14450 https://github.com/vim/vim/commit/41208884b8c1a73b42ddb6c1e5f008dae6aa0a83 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* 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>
generated by cgit (git 2.34.1) at 2025-06-24 10:27:34 +0000