aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/_meta.lua
diff options
context:
space:
mode:
authorGregory Anders <greg@gpanders.com>2021-07-24 10:28:16 -0600
committerGregory Anders <greg@gpanders.com>2021-07-24 10:28:16 -0600
commit860aedd06b6ea09c6337355226b9a93217fec531 (patch)
tree2e94681d1b0cfe748ac4741327661608a327ccf9 /runtime/lua/vim/_meta.lua
parent46009499afbb0232124072d775caa9552d0f71de (diff)
downloadrneovim-860aedd06b6ea09c6337355226b9a93217fec531.tar.gz
rneovim-860aedd06b6ea09c6337355226b9a93217fec531.tar.bz2
rneovim-860aedd06b6ea09c6337355226b9a93217fec531.zip
fix: source syncolors.vim after startup scripts
This fixes an issue introduced in #14771 (fix: source syncolors.vim before startup scripts) that affected highlights for users who set 'background' to light in their startup script. Because syncolor.vim checks for the value of &background, it was always setting up the 'dark' background colors, which looked wrong for users using light backgrounds. The primary benefit of #14771 is that it decoupled highlighting from the syntax engine. This is useful for e.g. treesitter, which still makes use of highlights even if the syntax engine is disabled. For this reason, it is still worthwhile to source syncolor.vim separately from synload.vim, which #14771 accomplishes. However, we should still source syncolor.vim after the user startup scripts, to ensure that we are respecting the options the user sets. Another corollary benefit is that this reduces some redundancy in highlight definitions, since we now only source syncolors.vim if the user did not already enable a colorscheme.
Diffstat (limited to 'runtime/lua/vim/_meta.lua')
0 files changed, 0 insertions, 0 deletions