mirrors/neovim
1
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2026-09-25 06:52:06 +00:00
Code Issues Packages Projects Releases Wiki Activity
34,951 Commits 12 Branches 63 Tags
d1f7672bc9c39bad8000bcf2e2ec6feff8787986
Commit Graph
615 Commits
Author SHA1 Message Date
zeertzjqAndré-Patrick BubelClaude Opus 4.5
 		d1f7672bc9 vim-patch:fc00006: runtime(sieve): preserve existing line endings in ftplugin (#37334) 
Only set fileformat=dos for new files; preserve existing line endings
when editing. This satisfies RFC 5228 for new files while avoiding
issues with version control and existing workflows.

The previous change (3cb4148) unconditionally set fileformat=dos, which
converts existing files with LF line endings to CRLF on save. This
causes issues with version control (entire file appears changed) and
breaks workflows where sieve files are stored with unix line endings.

Dovecot Pigeonhole (the main sieve implementation) has explicitly
accepted LF line endings since 2008 (commit 97b967b5):
  /* Loose LF is allowed (non-standard) and converted to CRLF */
This behavior has remained unchanged for almost 18 years.

closes: vim/vim#19144

https://github.com/vim/vim/commit/fc00006777594f969ba8fcff676e6ca1bcb43546

Co-authored-by: André-Patrick Bubel <code@apb.name>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-10 08:07:58 +08:00
zeertzjqandChristian Brabandt 8eba81182a vim-patch:5eb10c5: runtime(xml): update XML runtime files 
closes: vim/vim#19112

https://github.com/vim/vim/commit/5eb10c5359e05338050819b8229bd4c8af36d365

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2026-01-08 09:30:03 +08:00
zeertzjqandChristian Brabandt 6e3883adb8 vim-patch:c45e16a: runtime(zsh): Update runtime files 
closes: vim/vim#19113

https://github.com/vim/vim/commit/c45e16a939b5d924d13bf234a5905b5b599884fc

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2026-01-08 09:30:03 +08:00
zeertzjqandChristian Brabandt db210dd2a4 vim-patch:57352b2: runtime: mention subscription only ml, fix typo in maintainer email (#37222) 
https://github.com/vim/vim/commit/57352b279d4de492dee4be07d6bc4a116599bbac

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2026-01-03 23:27:49 +00:00
zeertzjqandPaulo Moura cde32b3307 vim-patch:cc71684: runtime(logtalk): Update Logtalk runtime files for the latest language spec (#37205) 
closes: vim/vim#19058

https://github.com/vim/vim/commit/cc71684ab0025e87b697ed0b359214061f143392

Co-authored-by: Paulo Moura <pmoura@logtalk.org>
 2026-01-03 08:23:21 +08:00
zeertzjqandChristian Brabandt ab20681c52 vim-patch:62d8f3d: runtime: Revert several "mark invalid contact addresses" commits (#37192) 
This reverts commits:
- 6b652a785033fd4164e049492a7327c1ed7c3e5f
- 2f689d5abde0ccddca9e20d8c93a0299bd054e32
- a025a46d4169587145fb54f04af349cd05cb6122

Several email addresses that are known to be valid caused bounces
due to an issue with my email setup. The previous commits incorrectly
marked these addresses as invalid. So revert the whole thing again.

https://github.com/vim/vim/commit/62d8f3dab5a0b30c31a8df86a973c5e59821a3f0

N/A patch:
vim-patch:2f689d5: runtime: mark more invalid email addresses

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2026-01-02 06:53:44 +08:00
zeertzjqandChristian Brabandt cabefb52ff vim-patch:a025a46: runtime: mark more invalid email addresses 
https://github.com/vim/vim/commit/a025a46d4169587145fb54f04af349cd05cb6122

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2026-01-01 08:23:03 +08:00
zeertzjqandChristian Brabandt 65e7aa9255 vim-patch:partial:2f689d5: runtime: mark more invalid email addresses 
https://github.com/vim/vim/commit/2f689d5abde0ccddca9e20d8c93a0299bd054e32

Skip colors/ and syntax/help_ru.vim: missing previous changes.

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2026-01-01 08:17:57 +08:00
Evgeni Chasnovski c339b83a4a feat(pack): hint in confirmation buffer that plugin is not active 
Problem: After `vim.pack.update()` it is not clear if plugin is active
  or not. This can be useful to detect cases when plugin was removed
  from 'init.lua' but there was no `vim.pack.del()`.

Solution: Add ` (not active)` suffix with distinctive highlighting to
  header of plugins that are not active.
  It will also be shown in in-process LSP document symbols to have quick
  reference about which plugins are not active.
 2025-12-28 18:39:26 +02:00
zeertzjqandScott McKendry 7f1d7271d5 vim-patch:9.1.2027: filetype: bicep filetype used for 2 bicep file types (#37130) 
Problem:  filetype: bicep filetype used for 2 bicep file types
Solution: Detect *.bicepparam files as bicep-param filetype, include
          new bicep-params and bicep filetype plugin
          (Scott McKendry)

The bicep language server handles parameter files differently than
regular bicep files. Treating them the same at the editor level leads to
false positive diagnostics in the editor.

References:

Bicep Language Constants:
- https://github.com/Azure/bicep/blob/51392d32ca2c8b94b1bb7a255e78e1d559d12573/src/Bicep.Core/LanguageConstants.cs#L23
VS Code Extension definition:
- https://github.com/Azure/bicep/blob/51392d32ca2c8b94b1bb7a255e78e1d559d12573/src/vscode-bicep/package.json#L47

closes: vim/vim#19026

https://github.com/vim/vim/commit/4e722fdfdd987c11136e3533bd65d0ed4d15f829

Co-authored-by: Scott McKendry <me@scottmckendry.tech>
 2025-12-28 00:16:20 +00:00
zeertzjqandStanislaw Gruszka dfcf03b1ba vim-patch:5e577c7: runtime(ftplugin): set different formatoptions for bpftrace 
Problem:   Comment formatting does not work by default for bpftrace.
Solution:  Change default 'formatoptions' similarly as C and many other
           languages.

closes: vim/vim#18996

https://github.com/vim/vim/commit/5e577c7aa8be05281da54e9377fc0ac4b7280a2b

Co-authored-by: Stanislaw Gruszka <stf_xl@wp.pl>
 2025-12-24 08:44:51 +08:00
zeertzjqandSergio Alejandro Vargas dfbbc6dd6b vim-patch:f958d35: runtime(julia): Update Julia runtime files (#36876) 
Port changes from JuliaEditorSupport/julia-vim made during 2022-2025.
Most notably:

- 88f178c Do not reset shiftwidth/expandtab at undo
- f17257a Allow else block in try/catch
- 7946ce3 Support public statements (added in Julia v1.11.0-DEV.469)

https://github.com/vim/vim/commit/f958d357237970728e448a23df4cf831f97a9ae9

Co-authored-by: Sergio Alejandro Vargas <savargasqu+git@unal.edu.co>
 2025-12-09 22:25:04 +08:00
zeertzjqandAaron Jacobs 58d5d97719 vim-patch:98ef843: runtime(rust): use textwidth=100 for the Rust recommended style (#36875) 
The help text here said 99 was the recommended style for the standard
library, but I can't find a citation for this anywhere. In contrast the
Rust Style Guide hosted on rust-lang.org
[says](https://doc.rust-lang.org/stable/style-guide/#indentation-and-line-width)
the maximum line width is 100, and rustfmt
[agrees](https://github.com/rust-lang/rust/blob/37aa2135b5d0936bd13aa699d941aaa94fbaa645/src/tools/rustfmt/src/config/options.rs#L570).

Having the two disagree causes an annoying off-by-one error in vim: if
you configure vim to highlight too-long lines then it will occasionally
complain about a line that rustfmt refuses to fix.

closes: vim/vim#18892

https://github.com/vim/vim/commit/98ef8433b654ee96c57b66348b767edc73a44406

Co-authored-by: Aaron Jacobs <jacobsa@google.com>
 2025-12-09 20:42:12 +08:00
zeertzjqandStanislaw Gruszka d6be2b3312 vim-patch:9.1.1957: filetype: bpftrace files are not recognized (#36838) 
Problem:  filetype: bpftrace files are not recognized
Solution: Detect *.bt files as btftrace filetype,
          include a btftrace filetype plugin (Stanislaw Gruszka)

closes: vim/vim#18866

https://github.com/vim/vim/commit/b60b33a9dc91569f803e5a4856244bd8414f1802

Co-authored-by: Stanislaw Gruszka <stf_xl@wp.pl>
 2025-12-06 20:02:16 +08:00
zeertzjqandDoug Kearns e7e3351954 vim-patch:89f422d: runtime(quarto): add missing loaded guard 
closes: vim/vim#18630

https://github.com/vim/vim/commit/89f422df41dd9073626ce08cc1b066539ed84fa1

Co-authored-by: Doug Kearns <dougkearns@gmail.com>
 2025-12-04 08:52:42 +08:00
zeertzjqandD. Ben Knoble c81ff490dc vim-patch:ffc7f8c: runtime(hog): set undo_ftplugin correctly, delete trailing whitespace 
closes: vim/vim#18727

https://github.com/vim/vim/commit/ffc7f8c9dac67cce6c020e8c4158972e2a88ce24

Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
 2025-12-04 08:51:25 +08:00
zeertzjqandJon Parise 3f8e51cee7 vim-patch:9.1.1936: filetype: Erlang lexical files are not recognized 
Problem:  filetype: Erlang lexical files are not recognized
Solution: Detect *.xrl files as leex filetype, include syntax and
          filetype plugins (Jon Parise).

leex is the lexical analyzer generator for Erlang. Its input file format
follows a section-based structure and uses the `.xrl` file extension.

This initial work includes file detection, an ftplugin (which inherits
the Erlang configuration), and a syntax definition.

Reference:
-  https://www.erlang.org/doc/apps/parsetools/leex.html

related: vim/vim#18819
closes: vim/vim#18832

https://github.com/vim/vim/commit/b087c5452b4c12bfc9e7f6cecbee34aab64c92d8

Co-authored-by: Jon Parise <jon@indelible.org>
 2025-12-01 10:11:34 +08:00
Yochem van Rosmalen e49a592595 fix(help): retry once if async parsing fails #36592 
Problem:
If the buffer changes during iteration of the query matches,
`get_node_text()` may fail, showing an error to the user.

Solution:
Use `pcall` to not propogate the error to the user. Retry once if an
error occurred.
 2025-11-20 15:29:55 -08:00
Evgeni Chasnovski ee3239fcb6 fix(pack): consistently use "revision" instead of "state" 
Problem: In some areas plugin's revision is named "state". This might be
  confusing for the users.

Solution: Consistently use "revision" to indicate "plugin's state on
  disk".
 2025-11-06 19:54:57 +02:00
zeertzjqandtocariimaa 16c8152229 vim-patch:7dfdc7f: runtime(sml): add filetype plugin, move options from indent to ftplugin (#36460) 
closes: vim/vim#18680

https://github.com/vim/vim/commit/7dfdc7f6cb802d5283e2e0eedb87932b9cd2cb33

Co-authored-by: tocariimaa <tocariimaa@pissmail.com>
 2025-11-06 00:09:34 +00:00
zeertzjqandAaron Jacobs 59a44caac6 vim-patch:eba5133: runtime(rust): Do not use rustfmt as 'formatprg' by default (#36361) 
This reverts commit 4ac995bf9366c6624a0724d19b2226f4c95694b3.

This was added in vim/vim#16807, with no explanation for why it was necessary beyond
"it's an example of an idea". It completely breaks `gq` for me—rustfmt doesn't
reflow comments so is not an appropriate tool here! Beyond that, formatting a
selection with rustfmt treats that selection as if it were an entire file,
throwing away any indentation.

For example, the commit causes `gq` to turn this:

```rust
pub fn foo() {
    // blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
}
```

into this:

```rust
pub fn foo() {
// blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
}

```

which is totally wrong. In contrast, if I clear `formatprg` then `gq` does the
right thing again:

```rust
pub fn foo() {
    // blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
    // blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
    // blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
    // blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
    // blah blah blah blah blah blah
}
```

related: vim/vim#16967
related: vim/vim#17055
closes: vim/vim#18640

https://github.com/vim/vim/commit/eba51337d4b8051b768164f3394d680742234ca8

Co-authored-by: Aaron Jacobs <jacobsa@google.com>
 2025-10-27 23:45:14 +00:00
zeertzjqandRiley Bruins 35d04394aa vim-patch:9.1.1878: filetype: Soy files are not recognized (#36346) 
Problem:  filetype: Soy files are not recognized
Solution: Detect *.soy files as soy filetype,
          include a soy filetype plugin (Riley Bruins)

closes: vim/vim#18640

https://github.com/vim/vim/commit/9fff99c3c28083dbe4dcb243309bf2b28c4cb82b

Co-authored-by: Riley Bruins <ribru17@hotmail.com>
 2025-10-27 02:52:56 +00:00
zeertzjqandDoug Kearns 1ccbaa6c25 vim-patch:5ffb23c: runtime(rst): Update b:undo_ftplugin variable 
The value of this variable is evaluated when the 'filetype' option is
changed and should be a command string that will undo any configuration
changes that the plugin has made.

See :help undo_indent for details

related: vim/vim#18566

https://github.com/vim/vim/commit/5ffb23c967189585b74bb9a031caf3b6ef7cce9c

Co-authored-by: Doug Kearns <dougkearns@gmail.com>
 2025-10-14 10:44:47 +08:00
Yochem van Rosmalen 25322a3a3b fix(help): only set url for help files in $VIMRUNTIME #36165 
Problem:
Checking if the tag is nvim-owned (defined in a $VIMRUNTIME/doc/*.txt
file) is too expensive for now without non-obvious workarounds

Solution:
Only set url extmarks for $VIMRUNTIME/doc/*.txt files.

Closes: #36163
 2025-10-13 11:08:37 -07:00
Yochem van Rosmalen 62d3a2110d fix(help): wrong tag url in third-party help docs #36115 
fix(help): only set url for nvim-owned tags

Problem:
1. gx on |nonexistingtag| opens
https://neovim.io/doc/user/helptag.html?nonexistingtag.
2. b:undo_ftplugin doesn't remove url extmarks.

Solution:
1. Check if the tag is defined in a help file in $VIMRUNTIME.
2. Solution: clear namespace for buffer in b:undo_ftplugin.
 2025-10-12 15:08:18 -07:00
zeertzjqandDaumantas Kavolis 1c4e0e5044 vim-patch:cd6e209: runtime(kerml): update KerML comments to handle more cases (#36060) 
closes: vim/vim#18502

https://github.com/vim/vim/commit/cd6e20965166b45d0f711289cd5252a545dd8a93

Co-authored-by: Daumantas Kavolis <daumantas.kavolis@sensmetry.com>
 2025-10-06 23:53:47 +00:00
zeertzjqandDaumantas Kavolis a4a8838178 vim-patch:9.1.1829: filetype: KerML and SysML files are not recognized (#36042) 
Problem:  filetype: KerML and SysML files are not recognized
Solution: Detect *.kerml as kerml filetype, detect *.sysml as sysml
          filetype, include a kerml and sysml filetype plugin
          (Daumantas Kavolis)

closes: vim/vim#18476

https://github.com/vim/vim/commit/b73ccf7ff0326ece9c942127c1965475ad71b78a

Co-authored-by: Daumantas Kavolis <daumantas.kavolis@sensmetry.com>
 2025-10-06 06:07:41 +08:00
Evgeni Chasnovski 2728b4efe0 feat(pack): add [[ and ]] mappings in confirmation buffer 
Problem: No easy/robust way to jump between plugin sections.

Solution: Add `[[` and `]]` mappings.
 2025-10-05 19:20:05 +03:00
zeertzjqandJan Claußen 2c76a50e20 vim-patch:9.1.1821: filetype: Not all PKL files are recognized (#36008) 
Problem:  filetype: Not all PKL files are recognized
Solution: Detect *.pcf as pkl filetype, detect using the pkl-lsp://
          protocol as pkl filetype, include PKL syntax script
          (Jan Claußen)

This adds basic syntax support for the new PKL language by Apple.

What works:
- Shebang support
- Comment support
- Integers (decimal, hex, octal and binary) support
- Floating point support including exponentials
- Basic datatype support
- Unicode escape delimiters
- Escape code support
- String interpolation
- Support up to five pounds for custom delimiters
- Folding of multi-line comments and blocks

What doesn't work:

  The language heavily uses parameterized type declarations, which can get
  very complex. It is very hard to highlight this properly. There is
  official Tree-sitter support for this. Since it is hard to pull this off
  in a vim syntax file, I opted for basic support of the data types.

References:
  https://github.com/apple/pkl-pantry

fixes: vim/vim#18271
closes: vim/vim#18274

https://github.com/vim/vim/commit/67a8f2945e54def2a9a94aad919e4f489595acb7

Co-authored-by: Jan Claußen <jan.claussen10@web.de>
 2025-10-04 06:01:16 +08:00
zeertzjqandJon Parise e7ff132708 vim-patch:9.1.1764: filetype: CODEOWNERS file not recognized (#35789) 
Problem:  filetype: CODEOWNERS file not recognized
Solution: Detect CODEOWNERS file as codeowners filetype, include a
          syntax and filetype plugin (Jon Parise).

CODEOWNERS files define code ownership rules for GitHub-hosted (and
other) repositories. The syntax is similar to 'gitignore' files but
differs in enough ways to warrant its own filetype.

References:
- https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

closes: vim/vim#18299

https://github.com/vim/vim/commit/817e4d3ee6b051477596ba1d86a2631d9fabc95b

Co-authored-by: Jon Parise <jon@indelible.org>
 2025-09-16 01:58:34 +00:00
Yochem van Rosmalen 47b0a718c3 feat(help): gx opens help tag in web browser #35778 
Problem:
`gx` does not work on tags in help buffers to open the documentation of that tag in the browser.

Solution:
Get the `optionlink`, `taglink` and `tag` TS nodes and set extmark "url" property.
`gx` then discovers the extmark "url" and opens it.
 2025-09-15 15:38:49 -07:00
zeertzjqandD. Ben Knoble e2ab5e1db7 vim-patch:81ca991: runtime(html): guard against an existing b:undo_ftplugin var (#35763) 
Filetype plugins should not assume they are the only file to execute on
behalf of a buffer's filetype: other filetypes may use them, and
dotted filetypes may cause multiple to run. When this occurs, they
should _build_ on their respective b:undo_ftplugin settings, not
overwrite each other.

For example, when using a dotted filetype wiki.markdown, the wiki
filetype plugins go first. Then, during the markdown filetype plugins,
the HTML plugin's unconditional assignment to b:undo_ftplugin trashes
any data previously stored there by the wiki filetype.

Follow the pattern elsewhere of assigning or appending conditionally.

closes: vim/vim#18267

https://github.com/vim/vim/commit/81ca9916d2fb2675a1a6da22fd68d26fb0ee8b8e

Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
 2025-09-15 08:27:55 +08:00
zeertzjqandLuca Saccarola c7a9404019 vim-patch:becf184: runtime(misc): removing saccarosium from maintainer list (#35740) 
closes: vim/vim#17848

https://github.com/vim/vim/commit/becf1844e03462b2c997689caafc77bc9c812252

Co-authored-by: Luca Saccarola <github.e41mv@aleeas.com>
 2025-09-13 01:18:18 +00:00
zeertzjqandDoug Kearns 91fa613fad vim-patch:6505dc6: runtime(nu): Add new Nushell runtime files 
See: https://github.com/elkasztano/nushell-syntax-vim

Thanks to Pete Cruz (@Petesta) for promoting this addition.

closes: vim/vim#18208

https://github.com/vim/vim/commit/6505dc69d3a663448045d653112aa52e74894327

Co-authored-by: Doug Kearns <dougkearns@gmail.com>
 2025-09-07 21:22:12 +08:00
zeertzjqandChristian Brabandt 63b53c8d15 vim-patch:dfcd9ac: runtime(ada): mark as unmaintained, fix a few issues with the ftplugin 
closes: vim/vim#18178

https://github.com/vim/vim/commit/dfcd9ac120fd40d7e869922cec0bb273e9bc154a

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2025-09-06 08:16:23 +08:00
zeertzjqandChristian Brabandt 26c9f31b91 vim-patch:f737ff8: runtime(hamster): do not globally set ignorecase 
related: vim/vim#15772

https://github.com/vim/vim/commit/f737ff8c88b5fb77050ba44d986ee20d59ad37be

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2025-09-06 08:15:58 +08:00
zeertzjq 8a2587be23 Merge pull request #35546 from zeertzjq/vim-a07a2f4 
vim-patch:a07a2f4: runtime(astro): catch json_decode() error when parsing tsconfig.json
 2025-08-30 08:14:15 +08:00
zeertzjqandRadu Dineiu 53802da38b vim-patch:f66674c: runtime(fstab): Added mtab support to fstab syntax. 
closes: vim/vim#18074

https://github.com/vim/vim/commit/f66674cf429aa1fac79e522b45372d7e3d37a902

Co-authored-by: Radu Dineiu <radu.dineiu@gmail.com>
 2025-08-24 20:08:15 +08:00
zeertzjqandChristian Brabandt 7e450aa383 vim-patch:b405c79: runtime(vim): set 'comments' based on script type (legacy/Vim9) (#35359) 
fixes: vim/vim#18000

https://github.com/vim/vim/commit/b405c790046fc6758bf4a90feb6a67c2411685a0

Co-authored-by: Christian Brabandt <cb@256bit.org>
 2025-08-17 01:26:37 +00:00
zeertzjqandD. Ben Knoble d395dc9d38 vim-patch:7270a5a: runtime(racket): update Racket runtime files 
This brings the upstream files to commit 9dc3bd3 (ftplugin: escape Vim
special characters when opening docs, 2025-08-09). Note that not all
upstream files are included.

closes: vim/vim#17956

https://github.com/vim/vim/commit/7270a5a8431e0209043f14dd3fa3ea479e4cddc6

Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
 2025-08-11 07:00:28 +08:00
Phạm Bình An 69cc16d917 vim-patch:adfea9b: runtime(help): Unset 'comments' and 'cms' options (#35232) 
Problem:  Vim's help file doesn't have any syntax for comments, but
          'comments' and 'commentstring' are still set in the help
          buffer.
Solution: Unset 'comments' and 'cms' in help buffer

closes: vim/vim#17889

https://github.com/vim/vim/commit/adfea9b4e68f39744fcb6ce7840e1c3c3b4637db
 2025-08-08 09:31:47 +00:00
Christian ClasonandSquibid d994be44d7 vim-patch:93f6454: runtime(openscad): add a filetype plugin 
closes: vim/vim#17902

https://github.com/vim/vim/commit/93f6454724ba62035f7292e4ec62f1bc96a7dc46

Co-authored-by: Squibid <me@zacharyscheiman.com>
 2025-08-07 17:16:22 +02:00
Evgeni Chasnovski 6e27200901 test(pack): add vim.pack tests 2025-08-02 15:00:42 +03:00
zeertzjqandphanium 1f7432a272 vim-patch:714671d: runtime(misc): use :hor :term to ensure new term window is split horizontally (#35064) 
Problem:  :term splits new window above in vim, but in nvim it change
          the buffer for current window
Solution: :hor term to ensure consistent splitting for Vim and Neovim

closes: vim/vim#17822

https://github.com/vim/vim/commit/714671de3538266233d3411e0e375dba7d83005c

Co-authored-by: phanium <91544758+phanen@users.noreply.github.com>
 2025-07-25 18:44:56 +08:00
Christian ClasonandRiley Bruins 8dfad04ce9 vim-patch:a2578e0: runtime(uc): include uc filetype plugin 
closes: vim/vim#17802

https://github.com/vim/vim/commit/a2578e08d53d72ab1943b760b0ac35cefb1fc132

Co-authored-by: Riley Bruins <ribru17@hotmail.com>
 2025-07-20 13:27:55 +02:00
Christian ClasonandRiley Bruins 8bccd07972 vim-patch:9.1.1549: filetype: pkl files are not recognized 
Problem:  filetype: pkl files are not recognized
Solution: detect *.pkl files as pkl filetype, include
          a filetype plugin (Riley Bruins)

References:
https://pkl-lang.org/
https://github.com/apple/pkl

closes: vim/vim#17751

https://github.com/vim/vim/commit/d128889b306680338dbfb54ccc1ff32dc114165d

Co-authored-by: Riley Bruins <ribru17@hotmail.com>
 2025-07-16 10:32:33 +02:00
Christian ClasonandRiley Bruins 4195b82ec9 vim-patch:9.1.1548: filetype: OpenFGA files are not recognized 
Problem:  filetype: OpenFGA files are not recognized
Solution: detect *.fga files as fga filetype, include an fga filetype
          plugin (Riley Bruins)

References:
https://github.com/openfga
https://marketplace.visualstudio.com/items?itemName=openfga.openfga-vscode

closes: vim/vim#17752

https://github.com/vim/vim/commit/0992f62fc18431296d3d5d6ab04317b8de4c76d9

Co-authored-by: Riley Bruins <ribru17@hotmail.com>
 2025-07-16 10:32:33 +02:00
Christian ClasonandRiley Bruins fa648731ec vim-patch:9a667b4: runtime(swig): add 'comments', 'commentstring' in filetype plugin 
Reference:
https://www.swig.org/Doc1.3/SWIG.html#SWIG_nn5

closes: vim/vim#17753

https://github.com/vim/vim/commit/9a667b4dba09aee7968f33686afcac99dab347df

Co-authored-by: Riley Bruins <ribru17@hotmail.com>
 2025-07-16 10:32:33 +02:00
Christian ClasonandRiley Bruins 694f634556 vim-patch:30df425: runtime(twig): include twig filetype plugin 
closes: vim/vim#17754

https://github.com/vim/vim/commit/30df42557cac48fe9337334f1c0479746a104076

Co-authored-by: Riley Bruins <ribru17@hotmail.com>
 2025-07-16 10:32:33 +02:00
Phạm Bình An 9789a3b854 revert: "fix(runtime): set 'foldmethod' for Lua ftplugin #34929" (#34947) 
This reverts commit 12276832ab.
 2025-07-16 06:15:16 +08:00