rneovim.git/runtime/syntax, branch userregs_2

vim-patch:7517a8c: runtime(lf): improve syntax script, add filetype plugin

2025-04-09T08:14:27+00:00

- Greatly improve detection and highlighting of command/shell regions,
  input-device key labels, escape sequences (@joelim-work)
- Add ftplugin for formatoptions, toggling comment areas
  (@andis-sprinkis)
- Add a few missing lf option keywords, rm. old non-working code, misc.
  formatting (@andis-sprinkis)

closes: vim/vim#17078

https://github.com/vim/vim/commit/7517a8cadfd0e70d0422955cbad4767f6a40f29d

Co-authored-by: Andis Spriņķis

vim-patch:9.1.1271: filetype: Power Query files are not recognized

2025-04-04T08:43:18+00:00

Problem:  filetype: Power Query files are not recognized
Solution: detect '*.pq' as pq filetype, include pq syntax and filetype
          plugin (Anarion Dunedain)

Microsoft Power Query provides a powerful data import experience that
encompasses many features. Power Query works with desktop Analysis
Services, Excel, and Power BI workbooks, in addition to many online
services, such as Fabric, Power BI service, Power Apps, Microsoft 365
Customer Insights, and more. A core capability of Power Query is to
filter and combine, that is, to mash-up data from one or more of a rich
collection of supported data sources. Any such data mashup is expressed
using the Power Query M formula language. The M language is a
functional, case sensitive language similar to F#.

Reference:
- Power Query M formula language overview:
  https://learn.microsoft.com/en-us/powerquery-m/

closes: vim/vim#17045

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

Co-authored-by: Anarion Dunedain

vim-patch:6099db9: runtime(sh): Update syntax file, command substitution opening paren at EOL

2025-04-04T08:43:18+00:00

Allow the opening parenthesis of a command substitution to appear at
EOL.

This fixes the issue raised in
https://github.com/vim/vim/issues/17026#issuecomment-2774112284.

closes: vim/vim#17044

https://github.com/vim/vim/commit/6099db9a60d1c047bf9c8feee3e1689c4e653250

Co-authored-by: Doug Kearns

vim-patch:9.1.1268: filetype: dax files are not recognized

2025-04-03T08:15:11+00:00

Problem:  filetype: dax files are not recognized
Solution: detect "*.dax" as dax filetype, include dax filetype and
          syntax plugin (Anarion Dunedain)

Data Analysis Expressions (DAX) is a formula expression language used in
Analysis Services, Power BI, and Power Pivot in Excel. DAX formulas
include functions, operators, and values to perform advanced
calculations and queries on data in related tables and columns in
tabular data models.

DAX language overview:
- https://learn.microsoft.com/en-us/dax/dax-overview

closes: vim/vim#17035

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

Co-authored-by: Anarion Dunedain

vim-patch:649a237: runtime(debversions): Add release name for Debian 15 - duke (#33207)

2025-03-31T13:54:02+00:00

https://lists.debian.org/debian-devel-announce/2025/01/msg00004.html

closes: vim/vim#17010

https://github.com/vim/vim/commit/649a237bc886a2b702e95d5d45f661d8db6025f8

Co-authored-by: James McCoy

vim-patch:1054b18: runtime(java): Make changes for JDK 24 in syntax script

2025-03-29T13:29:26+00:00

- "Demote" SecurityManager from the list of java.lang class
  types to javaLangDeprecated.
- Reintroduce supported syntax-preview-feature numbers 455
  and 476 as _new numbers_ 488 and 494, respectively.

References:
- https://openjdk.org/jeps/486 (Permanently Disable the Security Manager)
- https://openjdk.org/jeps/488 (Primitive Types in Patterns etc.)
- https://openjdk.org/jeps/494 (Module Import Declarations)

closes: vim/vim#16977

https://github.com/vim/vim/commit/1054b18291ce611932bc949b22b87b78f1975ca9

Co-authored-by: Aliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>

vim-patch:0dc9a0b: runtime(lf): add lf r34 keywords to syntax script

2025-03-29T13:29:26+00:00

closes: vim/vim#17002

https://github.com/vim/vim/commit/0dc9a0bc60d469f52db064fc88ed9d8938fb5cc3

Co-authored-by: Andis Spriņķis

vim-patch:9.1.1243: diff mode is lacking for changes within lines

2025-03-28T06:45:01+00:00

Problem:  Diff mode's inline highlighting is lackluster. It only
          performs a line-by-line comparison, and calculates a single
          shortest range within a line that could encompass all the
          changes. In lines with multiple changes, or those that span
          multiple lines, this approach tends to end up highlighting
          much more than necessary.

Solution: Implement new inline highlighting modes by doing per-character
          or per-word diff within the diff block, and highlight only the
          relevant parts, add "inline:simple" to the defaults (which is
          the old behaviour)

This change introduces a new diffopt option "inline:". Setting to
"none" will disable all inline highlighting, "simple" (the default) will
use the old behavior, "char" / "word" will perform a character/word-wise
diff of the texts within each diff block and only highlight the
differences.

The new char/word inline diff only use the internal xdiff, and will
respect diff options such as algorithm choice, icase, and misc iwhite
options. indent-heuristics is always on to perform better sliding.

For character highlight, a post-process of the diff results is first
applied before we show the highlight. This is because a naive diff will
create a result with a lot of small diff chunks and gaps, due to the
repetitive nature of individual characters. The post-process is a
heuristic-based refinement that attempts to merge adjacent diff blocks
if they are separated by a short gap (1-3 characters), and can be
further tuned in the future for better results. This process results in
more characters than necessary being highlighted but overall less visual
noise.

For word highlight, always use first buffer's iskeyword definition.
Otherwise if each buffer has different iskeyword settings we would not
be able to group words properly.

The char/word diffing is always per-diff block, not per line, meaning
that changes that span multiple lines will show up correctly.
Added/removed newlines are not shown by default, but if the user has
'list' set (with "eol" listchar defined), the eol character will be be
highlighted correctly for the specific newline characters.

Also, add a new "DiffTextAdd" highlight group linked to "DiffText" by
default. It allows color schemes to use different colors for texts that
have been added within a line versus modified.

This doesn't interact with linematch perfectly currently. The linematch
feature splits up diff blocks into multiple smaller blocks for better
visual matching, which makes inline highlight less useful especially for
multi-line change (e.g. a line is broken into two lines). This could be
addressed in the future.

As a side change, this also removes the bounds checking introduced to
diff_read() as they were added to mask existing logic bugs that were
properly fixed in vim/vim#16768.

closes: vim/vim#16881

https://github.com/vim/vim/commit/9943d4790e42721a6777da9e12637aa595ba4965

Co-authored-by: Yee Cheng Chin

vim-patch:f9f4e27: runtime(hyprlang): save and restore cpo setting in syntax script

2025-03-27T23:21:54+00:00

fixes: vim/vim#16970
closes: vim/vim#16973

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

Co-authored-by: Christian Brabandt

vim-patch:052b86b: runtime(solidity): update syntax script with error definitions

2025-03-27T23:21:42+00:00

closes: vim/vim#16978

References:
- https://docs.soliditylang.org/en/latest/contracts.html#transient-storage
- https://soliditylang.org/blog/2021/04/21/custom-errors/

https://github.com/vim/vim/commit/052b86ba6315e65eb034ac906128f9bd82d5f2d7

Co-authored-by: S0AndS0