Yakov Lerner wrote:
On 6/2/06, Georg Dahn <[EMAIL PROTECTED]> wrote:
> I use dark backgrounds (and therefore a light coloured foreground colour).
> As a consequence the new MatchParen highlight that is enabled
> by default in vim 7 is unreadable/annoying.
> I need to put the following in my ~/.vimrc to fix it:
>
> highlight MatchParen ctermbg=blue guibg=blue
>
> Shouldn't the above be done automatically when one does set bg=dark ?

This depends on the color scheme you are using. If the maintainer
does not update his color scheme, a default value is chosen. If the
background is darkcyan, the highlight is not visible, of course,
if the background is blue, then your value is a bad choice.

I don't think any single colorscheme defines MatchParen.
I haven't seen any single colorscheme that define MatchParen.
Do they ?
Yakov


Well, maybe it's time to write your own colourscheme, based on the one you already use (if you do) or on the "default" one (if you don't) and with something like

   if &bg == "dark"
      hi MatchParen ctermbg=blue guibg=blue
   endif

in it. No doubt you will expand on it in the future, as you tweak more highlight colours.

Give your new colorscheme a unique name (let's say georgdahn for example's sake) followed by the .vim extension common to Vim scripts, and store it at one of the following places:

   $VIM/vimfiles/colors/georgdahn.vim
      system-wide on any platform

   $HOME/vimfiles/colors/georgdahn.vim
      user-private on Windows

   $HOME/.vim/colors/georgdahn.vim
      user-private on Unix

(i.e., in the colors/ subdirectory of one of the directory trees named early in the 'runtimepath' option, but NOT in the tree headed by $VIMRUNTIME because any upgrade can silently add, delete or modify anything there).

(creating any required not-yet-existing directory in the process); then add the line

   colorscheme georgdahn

to your vimrc. Note that it is not recursive: a colorscheme may NOT use the :colorscheme command to invoke (and possibly modify) a different colorscheme.


Best regards,
Tony.

Reply via email to