On 01/12/08 19:04, Matt Wozniski wrote:
> On Mon, Dec 1, 2008 at 11:15 AM, Simon Ruderich wrote:
>> On Mon, Dec 01, 2008 at 04:11:29AM -0800, snitko wrote:
>>> Here's a screenshot:
>>> http://dl.getdropbox.com/u/113891/pics/vim_commit_message.png
>>> The commit message was always highlighted with white color, but
>>> recently it has turned into this weird thing. The color scheme file
>>> hasn't changed. How do I fix this?
>> If you mean the orange color, this is a recommendation of Git; the short
>> commit message should only be 50 characters long, the rest is in white so you
>> know when you are past 50 characters.
>>
>> The second line should always be empty so it's colored as error. The long
>> description starts in in the third line.
>>
>> If you want to changes this, remove these lines from gitcommit.vim (my
>> version
>> is from 2008 Apr 09).
>>
>> hi def link gitcommitSummary Keyword
>> hi def link gitcommitBlank Error
>
> Or, much nicer, adding
>
> hi def link gitcommitSummary Normal
> hi def link gitcommitBlank Normal
>
> to your ~/.vimrc - same effect, but the changes won't be reverted next
> time gitcommit.vim is upgraded.
>
> ~Matt
The above should appear in your vimrc after the ":colorscheme" command.
Alternately, you can use
hi ColorScheme * hi def link gitcommitSummary Normal
\ | hi def link gitcommitBlank Normal
(or any other link) in your vimrc before the ":colorscheme", to avoid
having them removed even if you change colorschemes after starting Vim,
and even if one of them uses "hi clear" before setting its own colors.
Best regards,
Tony.
--
"Intelligence has much less practical application than you'd think."
-- Scott Adams, Dilbert.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
