mercurial - How do I make BitBucket recognize line breaks in commit comments? -

i work mercurial, , use long(ish), multi-line commit comments.

recently, i've put project on bitbucket.org, , have noticed when commit comments appended issue pages (see this question information on how/when happens), newlines replaced spaces, while double-newlines stay double-newlines.

how should mark single-newlines in commit messages bitbucket acknowledges them? i'd in least-obtrusive way when read comments command line.

break paragraphs (generating <p> tags) blank line. break lines (generating <br> tag) ending first line 2 or more spaces, e.g.

line one␣␣ line 2 

bitbucket formats comments using markdown, has this paragraphs , line breaks:

paragraphs , line breaks

a paragraph 1 or more consecutive lines of text, separated 1 or more blank lines. (a blank line line looks blank line — line containing nothing spaces or tabs considered blank.) normal paragraphs should not indented spaces or tabs.

the implication of "one or more consecutive lines of text" rule markdown supports "hard-wrapped" text paragraphs. differs other text-to-html formatters (including movable type’s "convert line breaks" option) translate every line break character in paragraph <br /> tag.

when want insert <br /> break tag using markdown, end line 2 or more spaces, type return.

yes, takes tad more effort create <br />, simplistic "every line break <br />" rule wouldn’t work markdown. markdown’s email-style blockquoting , multi-paragraph list items work best — , better — when format them hard breaks.