On: Don't write documentation in Markdown

[dbalatero]

I like it, as it lets me format at 80-char breaks to prevent infinite line lengths for paragraphs of text. This makes Github diffs easier to read as well.

[khc → dbalatero]

except when you add one word and re-flow the entire paragraph

[ilammy → khc]

That's when semantic line-breaking comes into a picture. Put a line break before each new sentence and before each clause in a sentence. That makes the text much more diff-friendly, and tends to keep the line lengths at bay too.

[robinson-wall → khc]

Your editor should be able to help with that. For example in vim: `gqap` will reflow the current paragraph, or while in visual select mode you can use `gq` to reflow your selection).

[khc → robinson-wall]

that's exactly what causes the viewing diff problem that I was replying to

[Spivak → khc]

--word-diff=color is your friend in this case.

[CGamesPlay → robinson-wall]

This still ruins the diff view of the code, though. (e.g. git blame)