On Sat, Nov 3, 2012 at 3:41 AM, David Aguilar <davvid@xxxxxxxxx> wrote: > On Fri, Nov 2, 2012 at 11:38 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: >> Ramkumar Ramachandra wrote: >>> Jonathan Nieder wrote: >> >>>> Ram, what platform do your colleagues use? >>> >>> Red Hat Enterprise Linux 5. >> >> Oh, ok. In that case I blame habit. >> >> I think the best option you have is to just complain to your >> colleagues about the long lines. Then they would get a chance to >> explore what the UI currently offers and to complain to this list >> (perhaps via you :)) about missing features that would make their work >> easier. >> >> To put it another way: I don't see yet how a hypothetical "git commit >> --wrap-lines -m 'long message'" would make life easier than just >> running "git commit" and entering the message using $EDITOR. There's >> probably a UI or documentation bug lurking somewhere, so thanks for >> thinking about these things. >> >> Regards, >> Jonathan > > If your colleagues do not mind using a GUI then git-cola > might help them form better commit messages. > > It auto-wraps long lines and enforces a very clear distinction > between the one-line summary and extended description. vim also does this nicely with syntax highlighting turned on, though I do not know how this feature is triggered. Specifically, it wraps all lines at 72 characters; it colors line 1 yellow out to 50 characters and white after that; and it colors any text on line 2 with a red background (should be empty). Phil -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html