| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
compiler(rime_deployer): include new compiler, use it for '*.custom.yaml' files (vim/vim#14460)
https://github.com/vim/vim/commit/8a31de6dd275b3dc925fee556ccccd5db8ee2504
Co-authored-by: wzy <32936898+Freed-Wu@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#28360)
Problem: filetype: some requirements files are not recognized
Solution: Detect '*-requirements.txt', 'constraints.txt',
'requirements.in', 'requirements/*.txt' and 'requires/*.txt'
as requirements filetype, include pip compiler, include
requirements filetype and syntax plugin
(Wu, Zhenyu, @raimon49)
closes: vim/vim#14379
https://github.com/vim/vim/commit/f9f5424d3e75bbdb35aa48fa6f9241d9479b35e8
Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
Co-authored-by: raimon <raimon49@hotmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
runtime(java): Recognise non-ASCII identifiers (vim/vim#14543)
* runtime(java): Recognise non-ASCII identifiers
Also:
- Remove the already commented out and less general in its
definition javaFuncDef alternative.
- Stop recognising some bespoke {p,trace} debugging API.
Non-ASCII identifiers have been supported from the outset
of the Java language.
> An _identifier_ is an unlimited-length sequence of _Java
> letters_ and _Java digits_, the first of which must be a
> Java letter. An identifier cannot have the same spelling
> (Unicode character sequence) as a keyword . . . Boolean
> literal . . . or the null literal . . .
> . . . . . . . .
> Letters and digits may be drawn from the entire Unicode
> character set . . .
> . . . . . . . .
> A Java letter is a character for which the method
> Character.isJavaLetter . . . returns true. A Java
> letter-or-digit is a character for which the method
> Character.isJavaLetterOrDigit . . . returns true.
> . . . . . . . .
> The Java letters include . . . for historical reasons, the
> ASCII underscore (_) . . . and dollar sign ($) . . .
(Separate syntax tests will be written when particular parts
now touched will have been further improved.)
Reference:
https://javaalmanac.io/jdk/1.0/langspec.pdf [§3.8]
* Take on the maintenance of Java filetype and syntax files
https://github.com/vim/vim/commit/4052474a1bd2fe756bc7dc596d29d0d7581e35ae
Co-authored-by: Aliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
ftplugin(gdb): add matchit support
closes: vim/vim#14462
https://github.com/vim/vim/commit/556c62165963359f1b35f17a49913fc61c43f937
Co-authored-by: Wu, Zhenyu <wuzhenyu@ustc.edu>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
runtime(deb822sources): Add minimal ftplugin (vim/vim#14240)
Set comment related options and avoid automatic line wrapping.
https://github.com/vim/vim/commit/2708c0b5854faad2844454324431a593c1d2987a
Co-authored-by: James McCoy <jamessan@jamessan.com>
|
|
|
|
|
|
|
|
| |
runtime(rust): Respect no_plugin_maps and no_rust_maps globals (vim/vim#14221)
https://github.com/vim/vim/commit/ef21bcaab145d6b22fb7c823607de23700f82653
Co-authored-by: MyyPo <110892040+MyyPo@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
| |
runtime(r,rhelp,rmd,rnoweb,rrst): Update ftplugin, browsefilter labels (vim/vim#14126)
Use the standard format for browsefilter labels:
"File Description (*.ext1, *.ext2, *.ext3)"
https://github.com/vim/vim/commit/e93afc2e612647e79e1082096ffd6c61e01ac691
Co-authored-by: dkearns <dougkearns@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
runtime(sh): Update ftplugin, fix vim/vim#14101 (vim/vim#14102)
Add the 'b' flag to 'comments', so that the shebang line is not detected as comment.
Fixes vim/vim#14101.
https://github.com/vim/vim/commit/e84d2d4432cd6e43f2bb300d02abc90d551bcf4a
Co-authored-by: dkearns <dougkearns@gmail.com>
|
|
|
|
|
|
|
| |
runtime(misc): announce adoption of various runtime files
https://github.com/vim/vim/commit/f9ca139e3aa12dd03177ebba5eedcee4f0836f27
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Help outlines, invoked by `gO`, displays the help section titles in the
location list window. This feature is implemented by setting the buffer
lines after opening the window, but this implementation breaks the
assumption that the quickfix window texts are consistently constructed
by the quickfix list items. I think we can use the conceal feature here.
Using conceal here improves interoperability between quickfix plugins,
and also simplifies the outline implementation.
Originally reported at https://github.com/itchyny/vim-qfedit/issues/12
|
|
|
|
|
|
|
|
|
|
| |
runtime(asciidoc): include basic ftplugin
closes: vim/vim#13873
https://github.com/vim/vim/commit/1da0e85816718a1d45ca60b3581c62df4e352c91
Co-authored-by: Luca Saccarola <github.e41mv@aleeas.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
runtime(vim): Update syntax and ftplugin files (vim/vim#13924)
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.
https://github.com/vim/vim/commit/21ce159e05615fd139c564b734a4bffc9f3fdc4b
Co-authored-by: dkearns <dougkearns@gmail.com>
|
|
|
|
|
|
|
|
| |
Update runtime files
https://github.com/vim/vim/commit/71b6d3397649fed68ef587aa863fcbdf5fdb057a
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
|
|
| |
It's the "tree-sitter" project, but "treesitter" in our code and docs.
|
|
|
|
|
|
|
|
| |
runtime(hurl): add hurl filetype plugin(vim/vim#13921)
https://github.com/vim/vim/commit/772f8f5425132b133a1d0fb22b35c13b4e027b42
Co-authored-by: Melker Ulander <melker.ulander@pm.me>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Translate the Vim9 script Godot files to legacy.
`<scriptcmd>` is not ported yet, so replace it with `<Cmd>` and `<SID>`.
If it's ported, `<scriptcmd>call s:` can be used instead.
Includes changes from:
vim-patch:0daafaa7d99e (was partial, but is now pretty much fully ported)
vim-patch:9712ff1288f9
Co-authored-by: Maxim Kim <habamax@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
runtime(odin): include ftplugin, syntax and indent script (vim/vim#13867)
https://github.com/vim/vim/commit/211211052d0426394cbd5f42f3f3f78a64822e2a
Translate the files from Vim9 script to legacy Vim script. Notably:
- Prefer case-matching comparisons where needed.
- Save and restore `&cpo`.
- Make the functions script-local. (Pretty easy to use these in expr options now
since Vim 9.0 anyways)
Add a note after the header for each file stating that they're manually
translated.
Co-authored-by: Maxim Kim <habamax@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: vim/vim#6796
closes: vim/vim#8115
https://github.com/vim/vim/commit/68a89470693c7687d4e736ca056c05de632e3ac7
- Luaify the detection script:
- Split the `(*!m2foo*)` and `(*!m2foo+bar*)` detection into two Lua patterns,
as Lua capture groups cannot be used with `?` and friends (as they only work
on character classes).
- Use `vim.api.nvim_buf_call()` (ew) to call `modula2#SetDialect()` to ensure
`b:modula2` is set for the given bufnr.
- Skip the syntax screendump tests. (A shame as they test some of the detection
from `(*!m2foo+bar*)` tags, but I tested this locally and it seems to work)
- Port the synmenu.vim changes from Vim9 script. (Also tested this locally)
- (And also add the missing comma for `b:browsefilter` from earlier.)
Co-authored-by: Doug Kearns <dougkearns@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
runtime(ftplugin): Use "*" browsefilter pattern to match "All Files"
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 vim/vim#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: vim/vim#12759
https://github.com/vim/vim/commit/93197fde0f1db09b1e495cf3eb14a8f42c318b80
Co-authored-by: Doug Kearns <dougkearns@gmail.com>
|
|
|
|
|
|
|
|
| |
runtime(ruby): Update ftplugin and omni-complete (vim/vim#13805)
https://github.com/vim/vim/commit/d08059ab48b822a25060b8a486085371ddeebcf7
Co-authored-by: dkearns <dougkearns@gmail.com>
|
| |
|
|
|
|
|
|
|
|
| |
runtime(markdown): Fix folding of code blocks
https://github.com/vim/vim/commit/244f01658f9c60c71a776a2162c28ea93e102f12
Co-authored-by: Tim Pope <code@tpope.net>
|
|
|
|
|
|
|
|
| |
runtime(sass): Provide sass_recommended_style option
https://github.com/vim/vim/commit/a907c91992167e41da41008d4370e434e324cbf2
Co-authored-by: Tim Pope <code@tpope.net>
|
|
|
|
|
|
|
|
| |
runtime(gitcommit): Updates to ftplugin and syntax
https://github.com/vim/vim/commit/fda02d03c0cfe017e465c58b3baf8b3106287578
Co-authored-by: Tim Pope <code@tpope.net>
|
|
|
|
|
|
|
|
| |
runtime(git): Add small ftplugin
https://github.com/vim/vim/commit/48ddc6a6f86f1f42bdb49d308d72c15b0e90ce5a
Co-authored-by: Tim Pope <code@tpope.net>
|
|
|
|
|
|
|
|
|
|
| |
runtime(elixir): missing undo_ftplugin for indentkeys
fixup after vim/vim#13771
https://github.com/vim/vim/commit/d1cea036467ca55d7698378679a1e32c9f056d59
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
| |
runtime(elixir): fix indentation (vim/vim#13771)
https://github.com/vim/vim/commit/7e27411007378e005339ef37503697ae7e183da1
Co-authored-by: George Guimarães <george.guimaraes@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Runtime(fortran): updates to indent, syntax and ftplugin (vim/vim#13752)
* 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
https://github.com/vim/vim/commit/ea9964a36f948c1266d43dd8b3890c6f3bdd243d
Co-authored-by: Ajit-Thakkar <142174202+Ajit-Thakkar@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
runtime(erlang): add support for matchit plugin (vim/vim#13713)
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
https://github.com/vim/vim/commit/18ab6c3392ef83abf078042e233d085fe80b6c06
Co-authored-by: Csaba Hoch <csaba.hoch@gmail.com>
|
|
|
|
|
|
| |
Problem: Not all default highlight groups show their actual colors.
Solution: Refactor `vimhelp.lua` and apply it to all relevant lists (UI
groups, syntax groups, treesitter groups, LSP groups, diagnostic groups).
|
|
|
|
|
|
|
|
| |
runtime(logtalk): Update Logtalk runtime files for the latest language spec (vim/vim#13697)
https://github.com/vim/vim/commit/0f61943eb7769777a281e0f8b8ba4c5f46d13e84
Co-authored-by: Paulo Moura <pmoura@logtalk.org>
|
|
|
|
|
|
|
|
|
|
| |
runtime(sbt): do not set b:did_ftplugin before sourcing scala ftplugin(vim/vim#13657)
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.
https://github.com/vim/vim/commit/5a68cdf14915f20a1a6889cd0a76d29ecd374f24
Co-authored-by: Karl Yngve Lervåg <karl.yngve@lervag.net>
|
|
|
|
|
|
|
|
|
|
| |
runtime(fortran): update syntax and ftplugins
closes: vim/vim#13629
https://github.com/vim/vim/commit/6863084d3bd044700973e6180ccb1a044566ec46
Co-authored-by: Ajit-Thakkar <142174202+Ajit-Thakkar@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 vim/vim#1247 (which I found after writing this).
closes: vim/vim#13562
https://github.com/vim/vim/commit/2e31065a650015892179e520038bf2083a9519b6
Co-authored-by: Julien Marrec <julien.marrec@gmail.com>
Co-authored-by: Matěj Cepl <mcepl@cepl.eu>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: vim/vim#13533
https://github.com/vim/vim/commit/bc8f79d36a456054ed29f46585830af6d71f57c8
Co-authored-by: rhysd <lin90162@yahoo.co.jp>
|
|
|
|
|
|
|
|
| |
runtime(lynx): Update for Lynx 2.8.9 (vim/vim#13510)
https://github.com/vim/vim/commit/2c133f6c1a165a74678a89722ed8c42967c295e4
Co-authored-by: dkearns <dougkearns@gmail.com>
|
|
|
|
|
|
|
|
| |
Problem: No filetype support for xcompose files
Solution: Add filetype detection
closes: vim/vim#13508
https://github.com/vim/vim/commit/4f9074b96cc7efb1c829ca74902a851551dcf4e8
|