On 24/02/09 03:56, Caleb Cushing wrote: >> I've been using these settings: >> >> >> highlight DiffAdd cterm=NONE ctermfg=bg ctermbg=Green gui=NONE guifg=bg >> guibg=Green >> highlight DiffDelete cterm=NONE ctermfg=bg ctermbg=Red gui=NONE guifg=bg >> guibg=Red >> highlight DiffChange cterm=NONE ctermfg=bg ctermbg=Yellow gui=NONE guifg=bg >> guibg=Yellow >> highlight DiffText cterm=NONE ctermfg=bg ctermbg=Magenta gui=NONE guifg=bg >> guibg=Magenta > > I should just add these to my vimrc and see if it helps? > >
Well, you can (see after the horizontal dividing line below though), but
it might perhaps be better to start a custom colorscheme with them (so
you don't lose your "special highlights" if you try another colorscheme
then want to come back). You don't have to define every single default
highlight group in your colorscheme, you can build upon the default
colors, changing only the nondefault ones.
I'm attaching the colorscheme I use (mostly, but not only, in the GUI):
it isn't for general use, but you might view it as an example of a
colorscheme setting most colors to the default (hence its name). You can
compare it with the "default" colorscheme,
$VIMRUNTIME/colors/default.vim, which resets _all_ colors to the
defaults but defines none of them.
In any case, if the colors set for the Diff<something> highlight groups
by the commands at top aren't to your liking, then (for Console mode)
tweak the cterm= ctermfg= ctermbg= arguments (or, for GUI mode, the
correspoding gui= guifg= guibg= ones).
-----------------------------------------------------------------------
Another possibility would be, rather than adding the 4 ":highlight"
commands at top, to search the existing colorschemes for one with
support of diff highlights in Console mode, maybe as follows:
:0verbose vimgrep /\<hi\%[ghlight]\s\+Diff/ $VIMRUNTIME/colors/*.vim
which will select ":highlight" commands for those diff-something groups.
Then find a colorscheme in the lot which changes the cterm= ctermfg=
ctermbg= settings (or at least one of them) for those groups. You may
have to try several such schemes before you find one which you like.
After running the vimgrep command, ":cnext" finds the next hit,
":cnfile" goes to the next file; similarly ":cprev" ":cpfile" ":cfirst"
":clast" etc.
Note: At least one of them has distinct ":hi" lines for cterm and GUI,
which sometimes means two different ones for the same grooup.
Best regards,
Tony.
--
"Microwave oven? Whaddya mean, it's a microwave oven? I've been
watching Channel 4 on the thing for two weeks."
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
almost-default.vim
Description: application/octetstream
