On 2016-04-02, Bram Moolenaar wrote:
> The command is a bit of a misnomer, it actually only affects
> highlighting. The idea is that all the default highlight groups are
> reset to their default. If a previous color scheme change, for example
> "Special" then it gets set back to the default. Then the color scheme
> only needs to set the groups that are different from the default.
> See $VIMRUNTIME/syntax/syncolor.vim for details.
It seems to affect more than this, too. That is, it resets more
than the default highlight groups.
I have a syntax file that defines a new group, diaryUnderlined, used
by other commands in that file. The usual sequence of operations
when opening a diary is that colorscheme is set in my ~/.vimrc, then
syntax/diary.vim is sourced, and highlighting looks fine.
But I also use a system with an xterm that sends Co in response to a
query from vim (part of TermCap Ops, I think). When vim receives
that Co, it sets t_Co and re-executes the colorscheme, which then
clears the diaryUnderlined group and all the text highlighted with
that goes to Normal.
I fixed the problem by adding this to my syntax file, but it seems
that it should be unnecessary.
autocmd ColorScheme * hi diaryUnderlined term=underline cterm=underline
ctermfg=blue gui=underline guifg=#80a0ff
Regards,
Gary
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
