summaryrefslogtreecommitdiffstats
path: root/runtime/ftplugin
AgeCommit message (Collapse)Author
2024-03-02runtime(r,rhelp,rmd,rnoweb,rrst): Update ftplugin, browsefilter labels (#14126)dkearns
Use the standard format for browsefilter labels: "File Description (*.ext1, *.ext2, *.ext3)" Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-02-27runtime(sh): Update ftplugin, fix #14101 (#14102)dkearns
Add the 'b' flag to 'comments', so that the shebang line is not detected as comment. Fixes #14101. Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-02-19runtime(misc): announce adoption of various runtime filesChristian Brabandt
Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-02-14runtime(asciidoc): include basic ftpluginLuca Saccarola
closes: #13873 Signed-off-by: Luca Saccarola <github.e41mv@aleeas.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-28runtime(vim): Update syntax and ftplugin files (#13924)dkearns
Improve matching of line-continuations and interspersed comments. These are now also matched in multiline syntax command patterns, dictionary literals, and parenthesised expressions and argument lists. Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-27runtime(hurl): add hurl filetype plugin(#13921)Melker Ulander
Signed-off-by: Melker Ulander <melker.ulander@pm.me> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-16runtime(odin): include ftplugin, syntax and indent script (#13867)Maxim Kim
Note for Neovim Contributors: this is bundled as Vim9 Script. If you want to use this on Neovim, you need to convert the Vim9 scripts to Vim Script or Lua or leave it out. Signed-off-by: Maxim Kim <habamax@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-14runtime(ftplugin): Use "*" browsefilter pattern to match "All Files"Doug Kearns
Problem: The "*.*" browsefilter pattern only matches all files on Windows (Daryl Lee) Solution: Use "*" to filter on all platforms but keep "*.*" as the label text on Windows. (Fixes #12685, Doug Kearns) The *.* browsefilter pattern used to match "All Files" on Windows is a legacy of the DOS 8.3 filename wildcard matching algorithm. For reasons of backward compatibility this still works on Windows to match all files, even those without an extension. However, this pattern only matches filenames containing a dot on other platforms. This often makes files without an extension difficult to access from the file dialog, e.g., "Makefile" On Windows it is still standard practice to use "*.*" for the filter label so ftplugins should use "All Files (*.*)" on Windows and "All Files (*)" on other platforms. This matches Vim's default browsefilter values. This commit also normalises the browsefilter conditional test to check for the Win32 and GTK GUI features and an unset b:browsefilter. closes: #12759 Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-05patch 9.1.0013: Modula2 filetype support lackingv9.1.0013Doug Kearns
Problem: Modula2 filetype support lacking Solution: Improve the Modula-2 runtime support, add additional modula2 dialects, add compiler plugin, update syntax highlighting, include syntax tests, update Makefiles (Doug Kearns) closes: #6796 closes: #8115 Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Benjamin Kowarsch <trijezdci@users.noreply.github.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-01runtime(ruby): Update ftplugin and omni-complete (#13805)dkearns
Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-28runtime(markdown): Fix folding of code blocksTim Pope
2023-12-28runtime(sass): Provide sass_recommended_style optionTim Pope
2023-12-28runtime(gitcommit): Updates to ftplugin and syntaxTim Pope
2023-12-28runtime(git): Add small ftpluginTim Pope
2023-12-27runtime(elixir): missing undo_ftplugin for indentkeysChristian Brabandt
fixup after #13771 Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-27runtime(elixir): fix indentation (#13771)George Guimarães
Signed-off-by: George Guimarães <george.guimaraes@gmail.com> Signed-off-by: Mitchell Hanberg <mitch@mitchellhanberg.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-27runtime(context): update ConTeXt keywords and other minor fixes (#13778)Lifepillar
Update to the ConTeXt runtime files. Changes: 1. shared syntax files updated with `mtxrun --script interface --vim` using the latest ConTeXt LMTX. 2. fixed reference to `make` tag in the help file. 3. added `keepend` to mitigate issues with embedded Lua syntax (see below). 4. the latest revision date of each ConTeXt runtime file has been updated to the date of this commit. The issue about embedded Lua was reported by a user: >Take the following valid ConTeXt file: > \starttext > \ctxlua{context("Text generated from Lua.")} > \ctxlua{context("Another text generated from Lua.")} > \stoptext >On my Vim installation (including when I start Vim with `--clean`), the >closing bracket and curly braces on line 2 are highlighted red and the >syntax highlighting after that is off. >I was trying to dig a little bit into what was going on, using the >`synID()` and `synIDattr()` functions. It appears that the closing >bracket on line 2 is matched as a `luaParentError` instead of the end >of the `luaParen` region. Therefore, the `luaParen` region continues >all the way to the end of the file. The closing curly brace on line >2 is matched as a `luaError`, the 2nd `\ctxlua` on line 3 as >`luaParen`, etc. >This issue doesn't occur in a plain Lua file, where the closing bracket >is correctly matched as the end of the `luaParen` region. So it seems >that something goes wrong when the Lua syntax file is included in the >ConTeXt one. By adding `keepend`, the right parenthesis for some reason is still highlighted as a `luaParenError`, but at least the right curly brace should correctly end the Lua block. From what I've seen, I think it is very difficult to embed Lua syntax properly without help from the Lua syntax file (that is, without patching it). It has global rules such as: syn match luaParenError ")" syn match luaError "}" which make it difficult, if not impossible, to contain Lua syntax without `keepend` (and its limitations). Signed-off-by: Lifepillar <lifepillar@lifepillar.me> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-23Runtime(fortran): updates to indent, syntax and ftplugin (#13752)Ajit-Thakkar
* runtime update fortran.vim Add folding for newer features of Fortran * Runtime Update fortran.vim Add indent support for newer features of Fortran * Runtime Update fortran.vim Add newer features of Fortran to matchit patterns Signed-off-by: Ajit-Thakkar <142174202+Ajit-Thakkar@users.noreply.github.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-21runtime(erlang): add support for matchit plugin (#13713)Csaba Hoch
This commit updates the Erlang runtime files to be in sync with the `vim-erlang-runtime` repository. In particular, it adds the following commit (with some cleanup and simplification afterwards): https://github.com/vim-erlang/vim-erlang-runtime/commit/6ea8b85bc9c93b94c68ec53489a74f5687d898b0 Signed-off-by: Csaba Hoch <csaba.hoch@gmail.com> Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-16runtime(logtalk): Update Logtalk runtime files for the latest language spec ↵Paulo Moura
(#13697) Signed-off-by: Paulo Moura <pmoura@logtalk.org> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-11runtime(sbt): do not set b:did_ftplugin before sourcing scala ftplugin(#13657)Karl Yngve Lervåg
The `b:did_ftplugin` guard was set and prevented us from actually sourcing `ftplugin/scala.vim`. Since the latter script also sets the guard properly, we can simply remove the guard here. Signed-off-by: =?UTF-8?q?Karl=20Yngve=20Lerv=C3=A5g?= <karl.yngve+git@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-12-05runtime(fortran): update syntax and ftpluginsAjit-Thakkar
closes: #13629 Signed-off-by: Ajit-Thakkar <142174202+Ajit-Thakkar@users.noreply.github.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-11-25patch 9.0.2128: runtime(swig): add syntax and filetype pluginsv9.0.2128Julien Marrec
Add syntax and filetype plugins for SWIG (Simplified Wrapper Interface Generator) description files. The default syntax for .i files highlights comments in a reverse color scheme which doesn't look well. This syntax builds on vim's c++ syntax by adding highlighting for common swig directives and user defined directives. For an alternative syntax, see vimscript #1247 (which I found after writing this). closes: #13562 Co-authored-by: Matěj Cepl <mcepl@cepl.eu> Co-authored-by: Julien Marrec <julien.marrec@gmail.com> Signed-off-by: Julien Marrec <julien.marrec@gmail.com> Signed-off-by: Doug Kearns <dougkearns@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-11-14patch 9.0.2104: wast filetype should be replaced by wat filetypev9.0.2104rhysd
Problem: wast filetype should be replaced by wat filetype Solution: start using the official wat filetype name runtime: rename `wast` filetype to `wat` (Wasm text format) The problem is the name of the current filetype wast. When the plugin was initially created, the file extension for Wasm text format was not fixed and .wast was more popular. However, recently .wat became the official file extension for WebAssembly text (WAT) format and .wast is now a file extension for the unofficial WAST format, which is a superset of .wat for the convenience to describe the Wasm specification conformance tests. https://webassembly.js.org/docs/contrib-wat-vs-wast.html However for now, let's keep using the `wat` filetype even for the .wast extension, so that we at least do not lose the filetype settings and syntax highlighting. This can be adjusted later, if it turns out to have a separate need for. closes: #13533 Signed-off-by: rhysd <lin90162@yahoo.co.jp> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-11-11runtime(lynx): Update for Lynx 2.8.9 (#13510)dkearns
Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-11-11patch 9.0.2098: No filetype support for xcompose filesv9.0.2098ObserverOfTime
Problem: No filetype support for xcompose files Solution: Add filetype detection closes: #13508 Signed-off-by: ObserverOfTime <chronobserver@disroot.org> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-11-08runtime(wget): Update for Wget2 2.1.0 (#13497)dkearns
Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-11-04runtime(dist): centralize safe executable check and add vim library (#13413)D. Ben Knoble
Follow up to 816fbcc26 (patch 9.0.1833: [security] runtime file fixes, 2023-08-31) and f7ac0ef50 (runtime: don't execute external commands when loading ftplugins, 2023-09-06). This puts the logic for safe executable checks in a single place, by introducing a central vim library, so all filetypes benefit from consistency. Notable changes: - dist#vim because the (autoload) namespace for a new runtime support library. Supporting functions should get documentation. It might make life easier for NeoVim devs to make the documentation a new file rather than cram it into existing files, though we may want cross-references to it somewhere… - The gzip and zip plugins need to be opted into by enabling execution of those programs (or the global plugin_exec). This needs documentation or discussion. - This fixes a bug in the zig plugin: code setting s:tmp_cwd was removed in f7ac0ef50 (runtime: don't execute external commands when loading ftplugins, 2023-09-06), but the variable was still referenced. Since the new function takes care of that automatically, the variable is no longer needed. Signed-off-by: D. Ben Knoble <ben.knoble+github@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-26runtime(debian): update debian related runtime files (#13423)James McCoy
* Update Debian runtime files Add mantic as a supported Ubuntu release and move buster/kinetic to unsupported. Add syntax highlighting for deb822sources filetype. Add debsources ftplugin to set relevant comment options. Move common version information to shared/debversions.vim Closes #11934 Co-authored-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Co-authored-by: James Addison <jay@jp-hosting.net> Co-authored-by: Viktor Szépe <viktor@szepe.net> Signed-off-by: James McCoy <jamessan@jamessan.com> * Add myself as codeowner for Debian-related runtime files Signed-off-by: James McCoy <jamessan@jamessan.com> --------- Signed-off-by: James McCoy <jamessan@jamessan.com> Co-authored-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Co-authored-by: James Addison <jay@jp-hosting.net> Co-authored-by: Viktor Szépe <viktor@szepe.net> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-26patch 9.0.2071: objdump files not recognizedv9.0.2071Colin Kennedy
Problem: objdump files not recognized Solution: detect *.objdump files, add a filetype plugin Added the objdump file/text format closes: #13425 Signed-off-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Colin Kennedy <colinvfx@gmail.com>
2023-10-23runtime(vim): Update ftplugin - comment motions (#13412)dkearns
Fix the pattern used by comment-motion mappings to match the start of a block comment. Block-comment start lines were being ignored if the previous line contained a double-quote character anywhere in the line. Line comments should only be ignored if the previous line is a full-line comment and, therefore, part of the current block comment. Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-19runtime(json5): Add new ftplugin (#13385)dkearns
Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-19runtime(zig): Update Zig runtime files (#13388)Gregory Anders
Update runtime files from upstream (https://github.com/zig/zig.vim) at commit 54c216e5306a5c3878a60596aacb94dca8652ab9. Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-18runtime(systemd): allow for overriding systemd ftplugin settings (#13373)Enno
closes: #13357 Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-14runtime(tcsh): Update ftplugin (#13327)dkearns
Fix b:browsefilter deletion error when calling b:undo_ftplugin. Fixes #13167 Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-08runtime: make command name for &iskeywordprg more unique (#13297)Enno
See https://github.com/vim/vim/pull/13213/commits by @dkearns: Rename 'keywordprg' user command to ShKeywordPrg as this is just a leaking implementation detail. Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-10-06runtime(sh): Update ftplugin (#13213)dkearns
Rename 'keywordprg' user command to ShKeywordPrg as this is just a leaking implementation detail. Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-27runtime(rmd) Update ftplugin and syntax files (#13193)Jakson Alves de Aquino
ftplugin/rmd.vim: - Set 'commentstring' dynamically according to code region. syntax/rmd.vim: - Include syntax highlighting of fenced languages dynamically. - Add conceal char for line break. Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-25runtime(sh): only invoke bash help in ftplugin if it has been detected to be ↵Eisuke Kawashima
bash (#13171) Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-17runtime(kotlin): Add Kotlin runtime files (#13110)dkearns
Closes udalov/kotlin-vim#39 Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-15runtime(forth): Fix :unlet error in ftplugin (#13090)dkearns
Fixes #13089. Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-12runtime(rust): sync rust runtime files with upstream (#13075)Gregory Anders
Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-09patch 9.0.1886: Various Typosv9.0.1886Christian Brabandt
Problem: Various Typos Solution: Fix Typos This is a collection of typo related commits. closes: #12753 closes: #13016 Co-authored-by: Adri Verhoef <a3@a3.xs4all.nl> Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: Viktor Szépe <viktor@szepe.net> Co-authored-by: nuid64 <lvkuzvesov@proton.me> Co-authored-by: Meng Xiangzhuo <aumo@foxmail.com> Co-authored-by: Dominique Pellé <dominique.pelle@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-08runtime(perl): Update ftplugin and indent files (#13052)dkearns
Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-06runtime: don't execute external commands when loading ftpluginsChristian Brabandt
This is a followup to 816fbcc262687b81fc46f82f7bbeb1453addfe0c (patch 9.0.1833: [security] runtime file fixes) It basically disables that external commands are run on loading of the filetype plugin, **unless** the user has set the `g:plugin_exec = 1` global variable in their configuration or for a specific filetype the variable g:<filetype>_exec=1. There are a few more plugins, that may execute system commands like debchangelog, gitcommit, sh, racket, zsh, ps1 but those do at least do not run those commands by default during loading of the filetype plugin (there the command is mostly run as convenience for auto-completion or to provide documentation lookup). closes: #13034 Signed-off-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Tim Pope <vim@tpope.org>
2023-09-05runtime(ftplugin): allow to exec if curdir is in PATHAnton Sharonov
In case the current directory is present as valid $PATH entry, it is OK to call the program from it, even if vim curdir is in that same directory. (Without that patch, for instance, you will not be able to open .zip files while your current directory is /bin) closes: #13027 Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-04runtime: Fix problem of checking wrong cwd for ruby ftplugin (#13026)Anton Sharonov (ant0sha)
Co-authored-by: Anton Sharonov <anton.sharonov@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-09-01runtime(ruby): Update syntax, indent and ftplugin filesDoug Kearns
While making changes to the ruby ftplugin, slightly change the exepath() conditional from patch 9.0.1833 and move it after the :cd invocation. closes: 12981 closes: 12994 Signed-off-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Tim Pope <code@tpope.net> Co-authored-by: Doug Kearns <dougkearns@gmail.com>
2023-08-31patch 9.0.1833: [security] runtime file fixesv9.0.1833Christian Brabandt
Problem: runtime files may execute code in current dir Solution: only execute, if not run from current directory The perl, zig and ruby filetype plugins and the zip and gzip autoload plugins may try to load malicious executable files from the current working directory. This is especially a problem on windows, where the current directory is implicitly in your $PATH and windows may even run a file with the extension `.bat` because of $PATHEXT. So make sure that we are not trying to execute a file from the current directory. If this would be the case, error out (for the zip and gzip) plugins or silently do not run those commands (for the ftplugins). This assumes, that only the current working directory is bad. For all other directories, it is assumed that those directories were intentionally set to the $PATH by the user. Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-08-31runtime(forth): Update syntax and ftplugin files (#12976)dkearns
Signed-off-by: Christian Brabandt <cb@256bit.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 06:20:20 +0000