On Sun, 17 Jan 2010, MK wrote: > On Sat, 16 Jan 2010 14:42:13 +0100 > Tony Mechelynck <[email protected]> wrote: > > Let's say the vimComment highlight is not what you expect. Then > > > > :verbose hi vimComment > > Okay, so it is vim72/syntax/syncolor.vim > > Why would that override .vimrc? > > Sort of moot point for me suddenly tho -- since I am using the two > installations on one hd I decided to source my config from a file on a > mounted partition. Now the :hi commands are in a source'd file, they > override syncolor. But if I put them back directly into ~/.vimrc, > they are overriden by syncolor...kind of strange, probably an > irritation to new users if other people also experience this.
Maybe your own .vimrc is the culprit. I couldn't figure out why my 'expandtab' setting (or 'no-'?) in .vimrc was getting overridden, until I discovered that 'set binary' (added years and years ago before I knew better) was the one automatically resetting it. In this case, maybe check to ensure that your redefinition of 'hi vimComment' comes after any color- or syntax-related commands. If that doesn't work, maybe you have some auto command that resets syntax/color stuff that automatically resets 'hi vimComment' when you don't want it to. (though the fact that it works in the source'd file makes me think it's an ordering issue, not an autocommand issue.) Best, Ben
-- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
