4 ms·

> It's odd how neither this post, nor the spec, nor GitHub's "Mastering Markdown" help page[1], nor the more complete "Basic writing and formatting syntax" page

> It's odd how neither this post, nor the spec, nor GitHub's "Mastering Markdown" help page[1], nor the more complete "Basic writing and formatting syntax" page[2], mentions the fact that GitHub treats every newline as a hard break. Well, actually it does say that "Hard line breaks are for separating inline content within a block." https://github.github.com/gfm/#hard-line-break https://github.github.com/gfm/#hard-line-break So two spaces at the end of the line for a <br>, and an empty line for <p>.

jorams 10y ago
Right, but that's not what GFM does. GFM turns any single newline into a <br>.
- hashhar 10y ago
  Depends on where you use it. All file backed content (ie. repo data) does not use it, while the communications systems (PRs and issues) use it.
  - kivikakk 10y ago
    As of this announcement, file backed content _does_ use GFM (try a table!), but not the `hardbreaks` option.