On Mon, Apr 17, 2006 at 08:24:20AM +0200, Georg Dahn wrote:
> Hi!
>
> > Sorry, I meant to suggest trying
> >
> > :verbose hi Constant
> >
> > When I try this, it tells me that the Constant highlighting was set in
> > $VIMRUNTIME/syntax/syncolor.vim .
>
> > This file is :source'd after the :syn on command. In your gvimrc
> > file, do you have the lines to override the defaults before or after
> > this line?
>
> The 'syntax on' is in my vimrc file, which (AFAIK) is executed before
> gvimrc. After these highlights there are only two mappings.
Yes, your vimrc file should be executed first. I am still curious
about the result of
:verbose hi Constant
Along with
:scriptnames
This should give some clues as to what is going on.
> But your debugging line (let g:foo=...) shows, that the background is
> 'dark' there. It is dark at the beginning of vimrc, too. In gVim 6.4
> the value is 'light' in both cases, so I suppose the default value of
> 'background' was changed. This could be the problem, because the
> background is light when gVim is open and changing the value of
> 'background' changes several things.
>
> BTW, if I do 'colo default' in my vimrc I get the defaults for dark
> backgrounds but a white background, which makes the highlights
> unreadable. This happens, because the background is set to dark at
> that point, but this isn't, what the user expects.
Have you tried
:verbose set background
yet? If it is set to "dark" at the start of your vimrc file, this will
probably not tell you much ... but if it does tell you anything, it will
be worth knowing. Have you checked vim 6.4 and 7.0 for system vimrc and
gvimrc files? (See :version output for where vim will look for these.)
Of course,
:help 'background'
points out that vim cannot reliably guess the right value and suggests
setting it in your vimrc file. Maybe it is simpler to do this than to
figure out what is affecting the default value.
HTH --Benji Fisher
