On Wednesday, December 30, 2015 at 1:49:59 AM UTC-6, titus65 wrote:
> Hi,
>
>
> Since upgrading from 74488 to 74963 my custom highlighting
>
> rules are no longer effective
>
>
> Here is the vimrctest that demonstrates the problem:
>
> " comment this should appear in DarkCyan
> set nocompatible
> syntax on
> hi Comment term=bold ctermfg=6 guifg=DarkCyan
> hi Identifier term=underline ctermfg=4 guifg=Blue
> " EOF
>
>
>
> And the command is:
>
> vim --noplugin -i NONE -u ~/vimrctest ~/vimrctest
>
>
>
> When "set nocompatible" is uncommented then the highlighting rules are
>
> not effective If commented they work With 488-7 it makes no difference
>
> (as expected)
>
>
First: I can confirm that these lines do not change the highlighting, in
7.4.909.
When I use the indicated commands as a .vimrc, the comments are blue, and not
set from the test .vimrc. ":verbose hi Comment" gives:
Comment xxx term=bold ctermfg=1 guifg=Blue
Last set from C:\Program Files\vim\vim74\syntax\syncolor.vim
This is at least unexpected behavior. I'd certainly expect the .vimrc colors to
apply.
However, I see no difference with and without the nocompatible setting.
To work around this behavior, and in general, I would suggest putting any such
:hi commands either in a colorscheme file, or in a ColorScheme autocmd event.
Doing it this way does NOT show the problem.
--
--
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.
