colorscheme get's sourced twice resulting in lost custom highlighting

[Simon Morgan]

I had trouble with highlighting declerations in my .vimrc being lost when I
specified a colorscheme. Preben 'Peppe' Guldberg found the source of the
problem, here's what he had to say:

OK. I had a quick look at vim.out and see the following:

1) your vimrc is sourced and everything should be set up as you want it
2) $VIM/gvimrc is sourced
3) "syntax on" - eventually sourcing $VIMRUNTIME/syntax/synload.vim
4) your colour scheme is sourced again

In the last step, "i clear" is issued, clearing your highlighting.
Actually, your highlighting is only cleared because you also use a
colour scheme.

In my book, the $VIM/gvimrc could be improved. It contains a test that
reads

   if has("syntax") && (&t_Co > 2 || has("gui_running"))

I would change that to

   if has("syntax") && (&t_Co > 2 || has("gui_running")) && !syntax_on

which does not turn syntax on again, if it has already been done (by
you, eg. in your vimrc).

I also find the test for gui_running in a gvimrc redundant, but perhaps
the file is used as both a vimrc and a gvimrc.

[Simon Morgan (sjmorgan)]

Almost 4 months and still no response?

[Matt Zimmerman (mdz)]

We are dealing with thousands of bug reports at this time; regrettably yours was
overlooked.

[Ian Jackson (ijackson)]

Having read the vim documentation, it seems to me that it would be better simply
to replace `syntax on' with `syntax enable'. Can you check whether that works
for you ?

[Simon Morgan (sjmorgan)]

Nope. Unfortunately that still results in my custom highlighting being lost.

[Ian Jackson (ijackson)]

Could you supply (eg as an attachment) copies of your vim dotfiles ? Also, if
you could tell me what you see, and what you expect to see, that would be very
helpful.

Thanks.

[Simon Morgan (sjmorgan)]

Created an attachment (id=3849)
vimrc

[Simon Morgan (sjmorgan)]

I expect to see trailing whitespace highlighted in red.

[Simon Morgan (sjmorgan)]

Wakey wakey.

[Constantine Evans (cevans)]

After testing this in Edgy with Simon Morgan's .vimrc, I've found that this has been fixed, probably because gvimrc no longer contains the commands noted in the description.