News for hackers. Stuff that matters.
Re:A Note About Git Commit Messages by lallysingh on Friday January 07, 2011 @12:54PM (#2080302)
And let's not forget where else where the text may end up later.

I'm sure this message was fine in their mail reader:

http://www.ietf.org/mail-archive/web/manet/current/msg11520.... (chosen only b/c I was reading through the list this morning)

But now I must horizontally scroll :(

Re:A Note About Git Commit Messages by uxp on Friday January 07, 2011 @01:01PM (#2080361)
To be fair, thats a problem with the way browsers render anything inside the <pre> tag. If anything, it is an example of what people should do, not force unnecessary restrictions on the way they write text. Lest you might end up with:

    > This is a short paragraph that I am quoting that 
    > someone
    > else sent to me.
Re:A Note About Git Commit Messages by pjscott on Friday January 07, 2011 @01:10PM (#2080409)
Emacs has spoiled me. As soon as I saw your post, I felt a weird tingling urge to press M-q and fix it.
Re:A Note About Git Commit Messages by lallysingh on Friday January 07, 2011 @01:08PM (#2080395)
Indeed. We can fix all these systems... or stay at 72 columns.
Re:A Note About Git Commit Messages by chc on Friday January 07, 2011 @07:56PM (#2081767)
Or door 3: Let bad software stay bad, use good software instead and format our text naturally. If somebody chooses to use software that can't wrap text, that's fine for them personally — but I shouldn't have to deal with their artificial limitations.
Re:A Note About Git Commit Messages by notJim on Friday January 07, 2011 @01:13PM (#2080424)
Right-click, Inspect Element `white-space: normal`

No more scrolling.

Re:A Note About Git Commit Messages by billmcneale on Friday January 07, 2011 @04:25PM (#2081180)
The problem is with the way the archive web site decided to render this text.

From a web standpoint, the author of this email did the right thing: introduce very little formatting (only paragraph breaks) and leave it up to style sheets to render his text the way the reader wants it.

That's how you get the same text to render perfectly on a twenty column display (e.g. an old phone), a 30' inch monitor and everything in-between.

Introducing manual newlines at arbitrary points (e.g. 80 columns) is a bad practice that assumes that everyone will read your text on the same device.

Relevant explanation:

http://beust.com/weblog/2009/03/10/of-kindle-and-web-usabili...