summaryrefslogtreecommitdiff
path: root/spec.txt
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2014-12-27 21:18:27 -0800
committerJohn MacFarlane <jgm@berkeley.edu>2014-12-27 21:18:27 -0800
commit4cae33aebd586c69399e0e156b3842cacf36e8fa (patch)
tree7e2d73f937a7692499890770d236a7a16ef36a71 /spec.txt
parent130959973a9a8750dbaa63ab3cf04bb39d91fe7f (diff)
Clarify precedence of empty list item over setext header line.
CLoses #95.
Diffstat (limited to 'spec.txt')
-rw-r--r--spec.txt20
1 files changed, 13 insertions, 7 deletions
diff --git a/spec.txt b/spec.txt
index 3e96e6f..f1a3638 100644
--- a/spec.txt
+++ b/spec.txt
@@ -728,13 +728,19 @@ with no more than 3 spaces indentation, followed by a [setext header
underline](#setext-header-underline). The line of text must be
one that, were it not followed by the setext header underline,
would be interpreted as part of a paragraph: it cannot be a code
-block, header, blockquote, horizontal rule, or list. A [setext header
-underline](@setext-header-underline)
-is a sequence of `=` characters or a sequence of `-` characters, with no
-more than 3 spaces indentation and any number of trailing
-spaces. The header is a level 1 header if `=` characters are used, and
-a level 2 header if `-` characters are used. The contents of the header
-are the result of parsing the first line as Markdown inline content.
+block, header, blockquote, horizontal rule, or list.
+
+A [setext header underline](@setext-header-underline) is a sequence of
+`=` characters or a sequence of `-` characters, with no more than 3
+spaces indentation and any number of trailing spaces. If a line
+containing a single `-` can be interpreted as an
+empty [list item](#list-items), it should be interpreted this way
+and not as a [setext header underline](#setext-header-underline).
+
+The header is a level 1 header if `=` characters are used in the
+[setext header underline](#setext-header-underline), and a level 2
+header if `-` characters are used. The contents of the header are the
+result of parsing the first line as Markdown inline content.
In general, a setext header need not be preceded or followed by a
blank line. However, it cannot interrupt a paragraph, so when a