You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you are probably aware, there is a long-standing issue causing syntax highlighting to be messed up when switching between colorschemes that define highlight groups for syntax items (see, for example, altercation/solarized#102).
Such issue doesn't seem easy to solve, since (see :h hi-default), Vim offers the possibility to override syntax highlight groups in one's own vimrc, and it seems reasonable to assume that such commands should be persistent across colorscheme changes (or should they?), which is at odds with the idea of including such commands in colorschemes (where the reasonable behaviour is that their effects are wiped out when the colorscheme changes). In practice, many colorschemes define highlighting for syntax items, so it would be nice if that didn't cause issues. I don't know whether you consider this something that should or might be addressed by Vim (maybe, your opinion is that people are misusing colorschemes).
However, I'd like to report the following, which does look like a bug to me. Consider this test-vimrc defining three custom highlight groups:
As you are probably aware, there is a long-standing issue causing syntax highlighting to be messed up when switching between colorschemes that define highlight groups for syntax items (see, for example, altercation/solarized#102).
Such issue doesn't seem easy to solve, since (see
:h hi-default
), Vim offers the possibility to override syntax highlight groups in one's ownvimrc
, and it seems reasonable to assume that such commands should be persistent across colorscheme changes (or should they?), which is at odds with the idea of including such commands in colorschemes (where the reasonable behaviour is that their effects are wiped out when the colorscheme changes). In practice, many colorschemes define highlighting for syntax items, so it would be nice if that didn't cause issues. I don't know whether you consider this something that should or might be addressed by Vim (maybe, your opinion is that people are misusing colorschemes).However, I'd like to report the following, which does look like a bug to me. Consider this
test-vimrc
defining three custom highlight groups:Execute
vim -i NONE -u test-vimrc -N
. Then, switch to thedefault
colorscheme and look how the highlight groups are defined:That's the output:
Edit: added missing command.
The text was updated successfully, but these errors were encountered: