From 1bbbd5fad349624148779dbc08a9b00332afc1f4 Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Wed, 2 Jan 2019 10:14:11 -0800 Subject: Manual: make it clear that `hard_line_breaks` works in gfm. See #5195. --- MANUAL.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/MANUAL.txt b/MANUAL.txt index a81720eb5..9c1f2f9a2 100644 --- a/MANUAL.txt +++ b/MANUAL.txt @@ -4245,10 +4245,10 @@ We also support `commonmark` and `gfm` (GitHub-Flavored Markdown, which is implemented as a set of extensions on `commonmark`). Note, however, that `commonmark` and `gfm` have limited support -for extensions. Only those listed below (and `smart` and -`raw_tex`) will work. The extensions can, however, all be -individually disabled. -Also, `raw_tex` only affects `gfm` output, not input. +for extensions. Only those listed below (and `smart`, +`raw_tex`, and `hard_line_breaks`) will work. The extensions +can, however, all be individually disabled. Also, `raw_tex` +only affects `gfm` output, not input. `gfm` (GitHub-Flavored Markdown) : `pipe_tables`, `raw_html`, `fenced_code_blocks`, `auto_identifiers`, -- cgit v1.2.3