aboutsummaryrefslogtreecommitdiff
path: root/runtime/ftplugin
Commit message (Collapse)AuthorAge
* vim-patch:9.1.1231: filetype: SPA JSON files are not recognizedChristian Clason2025-03-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: filetype: SPA (single page application) JSON files are not recognized (used by pipewire and wireplumber) Solution: detect pipewire and wireplumber configuration files as spajson filetype, include filetype, indent and syntax scripts for this new filetype (David Mandelberg). I looked at all the files found by this command to see if the syntax highlighting looked reasonable: ``` find {~/.config,/etc,/usr/share}/{pipewire,wireplumber} -type f -name \*.conf ``` References: * pipewire config files: https://docs.pipewire.org/page_config.html * wireplumber config files: https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/conf_file.html and * https://pipewire.pages.freedesktop.org/wireplumber/daemon/locations.html closes: vim/vim#16950 https://github.com/vim/vim/commit/4e7b4308fb92628434bd7e07ab92910c33051431 Co-authored-by: David Mandelberg <david@mandelberg.org>
* fix(runtime): gO always says "Help TOC" #32971Justin M. Keyes2025-03-19
| | | | | | | Problem: gO always says "Help TOC". Solution: Use a generic title instead.
* vim-patch:11ab02c: runtime(go): use :term for keywordprg for nvim/gvimChristian Clason2025-03-19
| | | | | | | | | | | | | | | | | | | | Problem: - The document from `go doc` can be very long, and you can scroll if using `!` to run shell command in Gvim. - I realize that I didn't fully mimic behavior of default keywordprg in Nvim in the last commit. Solution: - Use builtin terminal for keywordprg in Gvim - In Nvim (both TUI and GUI), it should mimic the behavior of Vim `:term`, `:Man`, and `:help` closes: vim/vim#16911 https://github.com/vim/vim/commit/11ab02c819449eaeddc3d8d291f06bc73f428e91 Co-authored-by: Phạm Bình An <phambinhanctb2004@gmail.com> Co-authored-by: zeertzjq <zeertzjq@outlook.com>
* fix(help): remove runnable code virtual textChristian Clason2025-03-18
| | | | | | | | Problem: Virtual text indicating runnable code examples in help files is intrusive and non-configurable (and often denotes actually non-working examples). Solution: Remove virtual text.
* fix(runtime): E15: Invalid expression in lua file when `gf`phanium2025-03-18
| | | | | | | | | | | | | | Problem: after https://github.com/neovim/neovim/pull/32719, `gf` error in lua: ``` E15: Invalid expression: "v:lua.require"vim._ftplugin.lua".includeexpr()" E447: Can't find file "vim._ftplugin.lua" in path ``` Solution: * use single quote (no idea why there's two pair double quote in expression). * add missing `v:fname`.
* feat(runtime): Lua ftplugin 'includeexpr' #32719Phạm Bình An2025-03-17
| | | | | | | | | Problem: Current `'includeexpr'` in runtime/ftplugin/lua.vim doesn't work with Nvim Lua. Solution: Provide an improved 'includeexpr' for Lua in "ftplugin/lua.lua". Closes: https://github.com/neovim/neovim/issues/32490
* feat(runtime): Lua ftplugin sets 'omnifunc', 'foldexpr' #32697Phạm Bình An2025-03-15
| | | | | | | | | | | | Problem: - Many other ftplugin have defined 'omnifunc', but the Lua one doesn't define one, even though there is `vim.lua_omnifunc()` - Users may want "stupid" completion to fix Lua config with `nvim --clean` in case they breaks it - Nvim doesn't port Lua foldexpr from Vim Solution: - Set 'omnifunc' to 'v:lua.vim.lua_omnifunc' in ftplugin/lua.lua - Set 'foldexpr' to use treesitter
* vim-patch:96395e1: runtime(cs): Update C# runtime filesChristian Clason2025-03-15
| | | | | | | | closes: vim/vim#16884 https://github.com/vim/vim/commit/96395e15125502e6c29bc93c58d688a2bdc31300 Co-authored-by: Nick Jensen <nickspoon@gmail.com>
* vim-patch:d49ba7b: runtime(sh): set b:match_skip to ignore matches for ↵zeertzjq2025-03-10
| | | | | | | | | | | matchit (#32812) related: vim/vim#16801 closes: chrisbra/matchit#50 closes: vim/vim#16834 https://github.com/vim/vim/commit/d49ba7b92a14e6f3c1c413d396df72d36e934f78 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:42e498d: runtime(plsql): move fold option from syntax to filetype ↵Christian Clason2025-03-10
| | | | | | | | | | | plugin closes: vim/vim#16838 https://github.com/vim/vim/commit/42e498d9c41a0260ccddceeb2927c18b508eff54 Co-authored-by: Lee Lindley <lee.lindley@gmail.com> Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* vim-patch:9.1.1188: runtime(tera): tera support can be improved (#32799)Muntasir Mahmud2025-03-09
| | | | | | | | | | Problem: runtime(tera): tera support can be improved Solution: update tera filetype plugin, include a tera syntax script update the filetype test, update makemenu and synmenu vim scripts (MuntasirSZN) closes: vim/vim#16830 vim/vim@14da0fb
* vim-patch:62e8228: runtime(go): add 'keywordprg' and 'formatprg' to ftpluginChristian Clason2025-03-08
| | | | | | | | closes: vim/vim#16804 https://github.com/vim/vim/commit/62e822808e364c84e8abfbc4827bf6012e5b32e0 Co-authored-by: Phạm Bình An <phambinhanctb2004@gmail.com>
* vim-patch:9.1.1177: filetype: tera files not detectedChristian Clason2025-03-07
| | | | | | | | | | | | | Problem: filetype: tera files not detected Solution: detect '*.tera' files as tera filetype, include a simple filetype plugin (MuntasirSZN) closes: vim/vim#16806 https://github.com/vim/vim/commit/5daaf2326800ff0683a5be9a7f475667a4fc09db Co-authored-by: MuntasirSZN <muntasir.joypurhat@gmail.com>
* vim-patch:08a410f: runtime(vim): recognize <...> strings (and keys) for ↵zeertzjq2025-03-06
| | | | | | | | | | | 'keywordprg' (#32752) see :help E499 and :h key-notation closes: vim/vim#16795 https://github.com/vim/vim/commit/08a410f674a340f137623526bf8159d5a476f729 Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* vim-patch:0b82054: runtime(lua): Improve 'include' and make '*expr' ↵brianhuster2025-03-02
| | | | | | | | | | | | | | | functions script-local - Prevent 'include' from matching variable assignments as calls to require() and others. - Use script-local functions for 'includeexpr' and 'foldexpr'. - Formatting fixes. closes: vim/vim#16746 https://github.com/vim/vim/commit/0b8205484b703b4a5a569cd1b0ed876bbb13901f Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* vim-patch:00a00f5: runtime(lua): Update lua ftplugin and documentationbrianhuster2025-03-02
| | | | | | | | | | | | | | | | | | | Problem: - The doc says the default `g:lua_subversion` is 2, but in fact it is 3 (see `runtime/syntax/lua.vim`) - `includeexpr` doesn't work with module in `init.lua` Solution: - Update documentation - Assign value to option `&include` - Add function `LuaInclude` and assign it to `l:&includeexpr` closes: vim/vim#16655 https://github.com/vim/vim/commit/00a00f5d3fc8dcf08e959c207a90f5902abc6a08 Co-authored-by: brianhuster <phambinhanctb2004@gmail.com> Co-authored-by: dkearns <dougkearns@gmail.com>
* vim-patch:580e457: runtime(vim): make VimKeywordPrg even smarter for regexeszeertzjq2025-02-26
| | | | | | | | closes: vim/vim#16729 https://github.com/vim/vim/commit/580e457a2a5fa63b9be0bf5f2c81434e157bcc0a Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* vim-patch:094494b: runtime(vim): improve &keywordprg in ftpluginbrianhuster2025-02-26
| | | | | | | | | | | | | | | | | | | | - let keywordprg in vim filetype handle context-sensitive help calls by detecting the syntax group of the word under the cursor - reformat whitespace - add modeline related: vim/vim#16677 closes: vim/vim#16680 https://github.com/vim/vim/commit/094494bf2eef8d788944b2b00b3361feb545d3ae Co-authored-by: Konfekt <Konfekt@users.noreply.github.com> Co-authored-by: Andrew Radev <andrey.radev@gmail.com> Co-authored-by: "D. Ben Knoble" <ben.knoble+github@gmail.com> Co-authored-by: Gary Johnson <garyjohn@spocom.com> Co-authored-by: Tim Pope <code@tpope.net> Co-authored-by: Doug Kearns <dougkearns@gmail.com> Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.1140: filetype: m17ndb files are not detected (#32618)zeertzjq2025-02-25
| | | | | | | | | | | | | | | | | | | | Problem: filetype: m17ndb files are not detected Solution: detect m17ndb files as m17ndb filetype, include filetype, syntax and indent files for the new filetype (David Mandelberg). References: https://www.nongnu.org/m17n/manual-en/m17nDBFormat.html describes the format. https://git.savannah.nongnu.org/cgit/m17n/m17n-db.git/tree/ has examples of the files. closes: vim/vim#16696 https://github.com/vim/vim/commit/ed7d8e55ac232758fc14fd132994b4a09b19350b Also adjust the xkb parent pattern according to dev_vimpatch.txt. Co-authored-by: David Mandelberg <david@mandelberg.org>
* revert "feat(ftplugin): set 'omnifunc' of Lua to 'v:lua.vim.lua_omnifunc'" ↵Justin M. Keyes2025-02-23
| | | | | #32597 This reverts commit f398e3a61abbf802b49867d2f533be1b0725c0d7.
* feat(ftplugin): set Lua 'omnifunc' to vim.lua_omnifunc #32491Phạm Bình An2025-02-23
| | | | | | | | | | Problem: - Many other ftplugin have defined 'omnifunc', but the Lua one doesn't define one, even though there is `vim.lua_omnifunc()` - Users may want "stupid" completion to fix Lua config with `nvim --clean` in case they breaks it Solution: Set 'omnifunc' to 'v:lua.vim.lua_omnifunc' in ftplugin/lua.lua
* vim-patch:61af587: runtime(dockerfile): set comments in filetype pluginChristian Clason2025-02-22
| | | | | | | | closes: vim/vim#16698 https://github.com/vim/vim/commit/61af587f26f56be7d6b55f77e42cc89504942cc0 Co-authored-by: David Mandelberg <david@mandelberg.org>
* fix(runtime): avoid E31 in ftplugin (#32578)phanium2025-02-22
| | | fix: twice nunmap in ftplugin
* feat(treesitter): table of contents for checkhealth, markdown (#32282)Christian Clason2025-02-22
| | | | | | | | | | | Problem: It's difficult to navigate large structured text files (vim help, checkhealth, Markdown). Solution: Support `gO` for table of contents and `]]`/`[[` for moving between headings for all these filetypes using treesitter queries. Refactor: colorization of highlight groups is moved to the `help` ftplugin while headings-related functionality is implemented in a private `vim.treesitter` module for possible future use for other filetypes.
* vim-patch:3cb4148: runtime(sieve): set fileformat=dos in filetype pluginChristian Clason2025-02-21
| | | | | | | | | | | References: https://datatracker.ietf.org/doc/html/rfc5228#section-2.2 closes: vim/vim#16685 https://github.com/vim/vim/commit/3cb41489dc8856959c1d586217f141ce057dc373 Co-authored-by: David Mandelberg <david@mandelberg.org>
* vim-patch:27f5136: runtime(mail): add commentstring '> %s' to ftpluginChristian Clason2025-02-21
| | | | | | | | | | | | | | | | The new native commenting functionality is currently not used when editing mail. One could reasonably expect it to change the "quote" state of any given line in the mail (i.e. the preceding ">"), which would be very handy and feel natural when editing mail. Especially since the current file already uses "setlocal comments+=n:>". Solution: Add commentstring to `> %s` to be used in files of type mail. closes: vim/vim#16669 https://github.com/vim/vim/commit/27f51367613a150877e88d2379409bebdf32052b Co-authored-by: Lucas Eekhof <105216949+eekhof@users.noreply.github.com>
* vim-patch:106899e: runtime(dnsmasq): include simple filetype pluginChristian Clason2025-02-21
| | | | | | | | closes: vim/vim#16671 https://github.com/vim/vim/commit/106899eb21ac0adfa0e31229d921a5f81e6a7e22 Co-authored-by: dringsim <dringsim@qq.com>
* vim-patch:911742a: runtime(dosini): Add support for # comments to ftpluginChristian Clason2025-02-21
| | | | | | | | | | | | runtime/syntax/dosini.vim supports both ; and # as comments, and I think a bunch of the files detected as dosini do too, so add support for # to the ftplugin. closes: vim/vim#16681 https://github.com/vim/vim/commit/911742a975caf69c1e35a866288f58450eb476cd Co-authored-by: David Mandelberg <david@mandelberg.org>
* vim-patch:d7deeff: runtime(exports): include simple filetype pluginzeertzjq2025-02-14
| | | | | | | | closes: vim/vim#16625 https://github.com/vim/vim/commit/d7deeffe11f4db3cce19236ddb80831652a87e83 Co-authored-by: Matt Perry <matt@mattperry.com>
* vim-patch:407319f: runtime(samba): include simple filetype pluginzeertzjq2025-02-14
| | | | | | | | closes: vim/vim#16626 https://github.com/vim/vim/commit/407319fe89d5df2c732937474479803d67761879 Co-authored-by: Matt Perry <matt@mattperry.com>
* vim-patch:8f3277f: runtime(nroff): set define option & add matchit config in ↵Christian Clason2025-02-13
| | | | | | | | | | ftplugin closes: vim/vim#16619 https://github.com/vim/vim/commit/8f3277fbbe92ff0e93289fec4bf8e91841e4ae25 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0967: SpotBugs compiler setup can be further improvedzeertzjq2025-02-04
| | | | | | | | | | | | Problem: SpotBugs compiler can be further improved Solution: Introduce event-driven primitives for SpotBugs (Aliaksei Budavei) closes: vim/vim#16258 https://github.com/vim/vim/commit/2e252474c4df5018b9819d86ebb70bf3b1b1a1af Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com>
* vim-patch:9.1.0935: SpotBugs compiler can be improvedzeertzjq2025-02-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: SpotBugs compiler can be improved Solution: runtime(compiler): Improve defaults and error handling for SpotBugs; update test_compiler.vim (Aliaksei Budavei) runtime(compiler): Improve defaults and error handling for SpotBugs * Keep "spotbugs#DefaultPreCompilerTestAction()" defined but do not assign its Funcref to the "PreCompilerTestAction" key of "g:spotbugs_properties": there are no default and there can only be introduced arbitrary "*sourceDirPath" entries; therefore, this assignment is confusing at best, given that the function's implementation delegates to whatever "PreCompilerAction" is. * Allow for the possibility of relative source pathnames passed as arguments to Vim for the Javac default actions, and the necessity to have them properly reconciled when the current working directory is changed. * Do not expect users to remember or know that new source files ‘must be’ ":argadd"'d to be then known to the Javac default actions; so collect the names of Java-file buffers and Java-file Vim arguments; and let users providing the "@sources" file-lists in the "g:javac_makeprg_params" variable update these file-lists themselves. * Strive to not leave behind a fire-once Syntax ":autocmd" for a Java buffer whenever an arbitrary pre-compile action errors out. * Only attempt to run a post-compiler action in the absence of failures for a pre-compiler action. Note that warnings and failures are treated alike (?!) by the Javac compiler, so when previews are tried out with "--enable-preview", remember about passing "-Xlint:-preview" too to also let SpotBugs have a go. * Properly group conditional operators when testing for key entries in a user-defined variable. * Also test whether "javaExternal" is defined when choosing an implementation for source-file parsing. * Two commands are provided to toggle actions for buffer-local autocommands: - SpotBugsRemoveBufferAutocmd; - SpotBugsDefineBufferAutocmd. For example, try this from "~/.vim/after/ftplugin/java.vim": ------------------------------------------------------------ if exists(':SpotBugsDefineBufferAutocmd') == 2 SpotBugsDefineBufferAutocmd BufWritePost SigUSR1 endif ------------------------------------------------------------ And ":doautocmd java_spotbugs User" can be manually used at will. closes: vim/vim#16140 https://github.com/vim/vim/commit/368ef5a48c7a41af7fe2c32a5d5659e23aff63d0 Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com>
* docs(treesitter): fix TSNode:range() type signature #32224Riley Bruins2025-01-27
| | | | Uses an overload to properly show the different return type based on the input parameter.
* vim-patch:9.1.1042: filetype: just files are not recognizedChristian Clason2025-01-23
| | | | | | | | | | | | | 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>
* vim-patch:4335fcf: runtime(kconfig): updated ftplugin and syntax scriptChristian Clason2025-01-21
| | | | | | https://github.com/vim/vim/commit/4335fcfed1b0a29c07b10f97d1f309dd8f964de6 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:c2a967a: runtime(c): Update syntax and ftplugin filesChristian Clason2025-01-18
| | | | | | | | | | | | | | | | | | | | | | | | | - 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>
* fix(docs): replace `yxx` mappings with `g==` #31947Evgeni Chasnovski2025-01-15
| | | | | | | | 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'.
* refactor: use nvim.foo.bar format for autocommand groupsMaria José Solano2025-01-14
|
* refactor: use nvim.foo.bar format for namespacesMaria José Solano2025-01-14
|
* vim-patch:51754c8: runtime(editorconfig): set omnifunc to syntaxcomplete funcChristian Clason2025-01-11
| | | | | | | | closes: vim/vim#16419 https://github.com/vim/vim/commit/51754c8a498c39592250a077f56db89dd261995d Co-authored-by: Yochem van Rosmalen <git@yochem.nl>
* feat(docs): "yxx" runs Lua/Vimscript code examples #31904Riley Bruins2025-01-09
| | | | | `yxx` in Normal mode over a Lua or Vimscript code block section will execute the code. Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
* vim-patch:9.1.0998: filetype: TI assembly files are not recognized (#31929)zeertzjq2025-01-09
| | | | | | | | | | | | Problem: filetype: TI assembly files are not recognized Solution: inspect '*.sa' and assembly files and detect TI assembly files, include filetype plugin and syntax script for TI assembly files (Wu, Zhenyu) closes: vim/vim#15827 https://github.com/vim/vim/commit/4f73c07abff420bad9fa5befc2c284c00b984993 Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0995: filetype: shaderslang files are not detectedChristian Clason2025-01-08
| | | | | | | | | | | | | | | Problem: filetype: shaderslang files are not detected Solution: detect '*.slang' files as shaderslang filetype, include a filetype and syntax script (mtvare6) Reference: https://shader-slang.com/ closes: vim/vim#16387 https://github.com/vim/vim/commit/616219f684744bcfad61a53c13166cda9b141dea Co-authored-by: mtvare6 <mtvare6@proton.me>
* vim-patch:7ceaa8f: runtime(vim): Remove trailing comma from match_wordsChristian Clason2025-01-07
| | | | | | | | | fixes: vim/vim#16377 (`filetype plugin indent on` breaks matchit). closes: vim/vim#16389 https://github.com/vim/vim/commit/7ceaa8f3ddbaad75fa02f91c0b354661b38253cb Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* vim-patch:fc61cfd: runtime(vim): Update matchit pattern, no Vim9 short names ↵zeertzjq2025-01-03
| | | | | | | | | (#31843) Abbreviated :enum and :interface commands are no longer supported. https://github.com/vim/vim/commit/fc61cfd60e6d99765d1a68d39d6613e0917c7c56 Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* vim-patch:9.1.0986: filetype: 'jj' filetype is a bit impreciseChristian Clason2025-01-03
| | | | | | | | | | | | Problem: filetype: 'jj' filetype is a bit imprecise Solution: rename 'jj' filetype to 'jjdescription' (Gregory Anders) closes: vim/vim#16364 https://github.com/vim/vim/commit/58c44e8833365e1a777330491c2799ae324ed893 Co-authored-by: Gregory Anders <greg@gpanders.com>
* vim-patch:9.1.0982: TI linker files are not recognizedChristian Clason2024-12-31
| | | | | | | | | | | | | Problem: TI linker files are not recognized Solution: inspect '*.cmd' files and detect TI linker files as 'lnk' filetype, include a lnk ftplugin and syntax script (Wu, Zhenyu) closes: vim/vim#16320 https://github.com/vim/vim/commit/39a4eb0b2ca901b59800fad086550053556e59dc Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:9.1.0972: filetype: TI linker map files are not recognizedChristian Clason2024-12-29
| | | | | | | | | | | | | | | Problem: filetype: TI linker map files are not recognized Solution: detect TI linker map files as lnkmap filetype (Wu, Zhenyu) References: https://downloads.ti.com/docs/esd/SPRUI03A/Content/SPRUI03A_HTML/linker_description.html closes: vim/vim#16324 https://github.com/vim/vim/commit/5113831d16c05f3a8b47da0c6f95a641d5fc7b2e Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
* vim-patch:df67fc0: runtime(sh): set shellcheck as the compiler for supported ↵Christian Clason2024-12-29
| | | | | | | | | | shells closes: vim/vim#16311 https://github.com/vim/vim/commit/df67fc0e6994bc92f3d82edc6269e158875defad Co-authored-by: Luca Saccarola <github.e41mv@aleeas.com>
generated by cgit (git 2.34.1) at 2025-09-22 13:40:39 +0000