On Dec 9, 2011, at 8:41 AM, Jakub Narebski wrote: > Sidney San Martín <s@xxxxxxxxxxxx> writes: > >> *Nothing else* in my everyday life works this way anymore. Line >> wrapping gets done on the display end in my email client, my web >> browser, my ebook reader entirely automatically, and it adapts to >> the size of the window. > > The problem with automatic wrapping on the display is that there could > be parts of commit message that *shouldn't* be wrapped, like code > sample, or URL... and in plain text you don't have a way to separate > flowed from non-flowed part. > I usually lead code, URLs, and other preformatted lines like this with a few spaces. Markdown uses the same convention, and it looks like commits in this repo do too. The patch in my last email prints lines which begin with whitespace verbatim. How does that work? > Also with long non-breakable identifiers you sometimes need to wrap by > hand (or use linebreaking algorithm from TeX) or go bit over the limit > to make it look nice. > Could you elaborate on this? The patch uses strbuf_add_wrapped_text, which was already in Git. If an identifier is longer than the wrap width, it leaves it alone. > BTW. proper editor used to create commit message can wrap it for you > ;-). Only if everybody else in the world does it too! And only if I never care about seeing my commits at any width besides 80 columns. > -- > Jakub Narębski > -- 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