rneovim.git/runtime/syntax/synload.vim, branch usermarks Neovim fork with Rahm's personal hacks. vim-patch:8.2.4741: startup test fails 2022-08-23T09:48:12+00:00 zeertzjq zeertzjq@outlook.com 2022-08-23T05:03:00+00:00 7afc17dec17bcc40c646b796f05d373e46916dd7 Problem: Startup test fails. Solution: Avoid an error for verbose expansion. Fix that the "0verbose" command modifier doesn't work. https://github.com/vim/vim/commit/60895f3e36def9beb7d5463e792e5154ad9a7a0a Most code changes has already been ported. 
Problem:    Startup test fails.
Solution:   Avoid an error for verbose expansion.  Fix that the "0verbose"
            command modifier doesn't work.
https://github.com/vim/vim/commit/60895f3e36def9beb7d5463e792e5154ad9a7a0a

Most code changes has already been ported.
vim-patch:75ab590f8504 (#18170) 2022-04-19T13:14:17+00:00 Christian Clason c.clason@uni-graz.at 2022-04-19T13:14:17+00:00 0124a7bfa9e27796e561cb0b3a045b9327bf7077 Update runtime files https://github.com/vim/vim/commit/75ab590f8504a8912ca0b8c58f6b897bb7a34f07 omit builtin.txt change to `expand()` (depends on 8.2.4726) 
Update runtime files
https://github.com/vim/vim/commit/75ab590f8504a8912ca0b8c58f6b897bb7a34f07

omit builtin.txt change to `expand()` (depends on 8.2.4726)
 fix(highlight): remove syncolor.vim 2021-07-27T20:14:30+00:00 Gregory Anders greg@gpanders.com 2021-07-27T16:46:24+00:00 9afa0d25a66f849452f498bd45e2f443f5010635 Remove syncolor.vim in favor of defining the default highlight groups directly in `init_highlight`. This approach provides a number of advantages: 1. The highlights are always defined, regardless of whether or not the syntax regex engine is enabled. 2. Redundant sourcing of syntax files is eliminated (syncolor.vim was often sourced multiple times based on how the user's colorscheme file was written). 3. The syntax highlighting regex engine and the highlight groups themselves are more fully decoupled. 4. Removal of the confusing `:syntax on` / `:syntax enable` dichotomy (they now both do the same thing). This approach also correctly solves a number of bugs related to highlighting (#15176, #12573, #15205). 
Remove syncolor.vim in favor of defining the default highlight groups
directly in `init_highlight`. This approach provides a number of
advantages:

1. The highlights are always defined, regardless of whether or not the
   syntax regex engine is enabled.
2. Redundant sourcing of syntax files is eliminated (syncolor.vim was
   often sourced multiple times based on how the user's colorscheme file
   was written).
3. The syntax highlighting regex engine and the highlight groups
   themselves are more fully decoupled.
4. Removal of the confusing `:syntax on` / `:syntax enable` dichotomy
   (they now both do the same thing).

This approach also correctly solves a number of bugs related to
highlighting (#15176, #12573, #15205).
fix: source syncolors.vim before startup scripts 2021-07-15T02:51:36+00:00 Gregory Anders greg@gpanders.com 2021-06-11T03:59:10+00:00 0bcf96bf0bf1136aa4fb09dd86461312a2bc4fbb This fixes an issue (#12573) where colorscheme files are sourced twice upon startup. This occurs when the startup script calls `:colorscheme`, which sets the `g:colors_name` global variable. When syntax highlighting is enabled in `syn_maybe_enable()` the `syntax.vim` script is sourced which in turn sources `synload.vim`. This script checks to see if `g:colors_name` is set and, if so, runs exe "colors " . colors_name This is done to ensure that highlight groups are defined before enabling the syntax highlighting engine. Instead, source syncolors.vim before the startup scripts which sets up default highlights and only load the full syntax engine after the startup scripts or when the user runs `:syntax on`. Add a guard variable `did_syncolor` to prevent syncolor.vim from being sourced twice and remove the line mentioned above from synload.vim so that the colorscheme file is not re-sourced when the syntax engine is loaded. 
This fixes an issue (#12573) where colorscheme files are sourced twice
upon startup. This occurs when the startup script calls `:colorscheme`,
which sets the `g:colors_name` global variable. When syntax highlighting
is enabled in `syn_maybe_enable()` the `syntax.vim` script is sourced
which in turn sources `synload.vim`. This script checks to see if
`g:colors_name` is set and, if so, runs

    exe "colors " . colors_name

This is done to ensure that highlight groups are defined before enabling
the syntax highlighting engine.

Instead, source syncolors.vim before the startup scripts which sets up
default highlights and only load the full syntax engine after
the startup scripts or when the user runs `:syntax on`. Add a guard
variable `did_syncolor` to prevent syncolor.vim from being sourced
twice and remove the line mentioned above from synload.vim so that
the colorscheme file is not re-sourced when the syntax engine is loaded.
feat(runtime): Allow lua to be used in syntax 2021-06-10T19:01:03+00:00 shadmansaleh shadmansaleh3@gmail.com 2021-06-02T15:08:28+00:00 f000251e087637d1add3678184ada80bef432fa9 






vim-patch:2c7f8c574f1f
2021-04-29T01:29:56+00:00

Jan Edmund Lazo
jan.lazo@mail.utoronto.ca

2021-04-28T03:14:29+00:00

c2635665c5a378dc8ed14b0199202fa86b226ad9

Update runtime files
https://github.com/vim/vim/commit/2c7f8c574f1f8723d59adca3fec8fb89c41cf8c9

Omit the following line for man.vim:
hi def link manFooter PreProc





Update runtime files
https://github.com/vim/vim/commit/2c7f8c574f1f8723d59adca3fec8fb89c41cf8c9

Omit the following line for man.vim:
hi def link manFooter PreProc







vim-patch:25de4c232d58
2017-04-28T23:53:42+00:00

Justin M. Keyes
justinkz@gmail.com

2017-04-28T23:53:03+00:00

024ff6b80831a27d2f6571006eb6fdf94d95f882

Updated runtime files.

https://github.com/vim/vim/commit/25de4c232d580583feadae11ab34e3cc6333c350





Updated runtime files.

https://github.com/vim/vim/commit/25de4c232d580583feadae11ab34e3cc6333c350







vim-patch:fc39ec
2016-04-17T06:06:24+00:00

David Barnett
davidbarnett2@gmail.com

2016-04-17T00:33:36+00:00

2895883154f4bbf9394e89acb3a86ee75255231b

Update runtime files.

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





Update runtime files.

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







re-integrate runtime/  vim-patch:0  #938
2014-07-29T02:12:31+00:00

Justin M. Keyes
justinkz@gmail.com

2014-07-11T04:05:51+00:00

a98a6996c291b3e300d27b791eded9eed333d677

Vim runtime files based on 7.4.384 / hg changeset 7090d7f160f7

Excluding:
  Amiga icons (*.info, icons/)
  doc/hangulin.txt
  tutor/
  spell/
  lang/ (only used for menu translations)
  macros/maze/, macros/hanoi/, macros/life/, macros/urm/
      These were used to test vi compatibility.
  termcap
      "Demonstration of a termcap file (for the Amiga and Archimedes)"

Helped-by: Rich Wareham <rjw57@cam.ac.uk>
Helped-by: John <john.schmidt.h@gmail.com>
Helped-by: Yann <yann@yann-salaun.com>
Helped-by: Christophe Badoit <c.badoit@lesiteimmo.com>
Helped-by: drasill <github@tof2k.com>
Helped-by: Tae Sandoval Murgan <taecilla@gmail.com>
Helped-by: Lowe Thiderman <lowe.thiderman@gmail.com>





Vim runtime files based on 7.4.384 / hg changeset 7090d7f160f7

Excluding:
  Amiga icons (*.info, icons/)
  doc/hangulin.txt
  tutor/
  spell/
  lang/ (only used for menu translations)
  macros/maze/, macros/hanoi/, macros/life/, macros/urm/
      These were used to test vi compatibility.
  termcap
      "Demonstration of a termcap file (for the Amiga and Archimedes)"

Helped-by: Rich Wareham <rjw57@cam.ac.uk>
Helped-by: John <john.schmidt.h@gmail.com>
Helped-by: Yann <yann@yann-salaun.com>
Helped-by: Christophe Badoit <c.badoit@lesiteimmo.com>
Helped-by: drasill <github@tof2k.com>
Helped-by: Tae Sandoval Murgan <taecilla@gmail.com>
Helped-by: Lowe Thiderman <lowe.thiderman@gmail.com>