On Mon, Dec 1, 2008 at 6:48 PM, snitko wrote:
>
> Great, thank you. Btw, since when second line in git should be empty?
See man git-commit
DISCUSSION
Though not required, it´s a good idea to begin the commit message with
a single short (less than 50 character) line summarizing the change,
followed by a blank line and then a more thorough description.
Also, check out the gitcommit.vim author's blog post about the
rationale for this syntax file:
http://www.tpope.net/node/106
> I thought long description starts on the second line, actually. And,
> btw, the red color there - it's not the second line. It's the same
> first line, vim just automatically moved it to the next line, but
> there's no \n symbols there.
No, if it's highlighted in red, there must be a newline there. Vim
probably added it for you, thanks to 'textwidth' and 'formatoptions' -
the textwidth used for gitcommit is 72, which so vim would have
automatically wrapped that line - the last 'e' in "white" would be the
71st character on the line.
~Matt
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
