On 13.12.2011 04:14, Michael Haggerty wrote:
On 12/12/2011 11:16 PM, Frans Klaver wrote:
Wrapped code as in auto-wrapped? Or as in manually wrapped? Python
programmers have significant white space, but you can still hard wrap
stuff, as long as the next statement is properly indented.
I meant as in auto-wrapped and also not as a permanent change but
something done to a long line on output to the screen.
FWIW I think automatic wrapping of commit messages is a bad idea. I
wrap my commit messages deliberately to make them look the way I want
Which you still can do (since hard line endings would not be ignored).
On displays wider than your line limit you will still see it exactly
like intended. Only on narrow displays your commit message would look
bad, admittedly even worse than cut-off lines.
them to look. The assumption of an 80-character display has historical
reasons, but it is also a relatively comfortable line-width to read
(even on wider displays). And given that commit messages sometimes
contain "flowable" paragraph text, sometimes code snippets, sometimes
ASCII art, etc, no automatic wrapping will work correctly unless
everybody agrees that commit messages must be written in some specific
form of markup (or lightweight markup). And I can't imagine such a
thing ever happening.
With that assumption everyone could be happy with automatic wrapping of
lines on screen output. You can hard wrap and it will look exactly as
intended. In the same commit message you could also just write a
paragraph without hitting the return-key at all and have a commit
message that looks good in web browsers and too narrow gitk windows.
--
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