aboutsummaryrefslogtreecommitdiff
path: root/spec.txt
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2015-06-08 11:00:25 -0700
committerJohn MacFarlane <jgm@berkeley.edu>2015-06-08 11:01:21 -0700
commit5976351c4da21f429648abf986954ad45c9fbcd7 (patch)
treee2f65042233e0c6f6a4172697ade73f936e6d368 /spec.txt
parent3d6172e310056fe88ea18b8f369ef1b2171aa65b (diff)
Clarified lazy block quote examples. (Closes #328.)
Diffstat (limited to 'spec.txt')
-rw-r--r--spec.txt25
1 files changed, 22 insertions, 3 deletions
diff --git a/spec.txt b/spec.txt
index 6fde458..4fff84d 100644
--- a/spec.txt
+++ b/spec.txt
@@ -2335,9 +2335,16 @@ foo</p>
</blockquote>
.
-Laziness only applies to lines that are continuations of
-paragraphs. Lines containing characters or indentation that indicate
-block structure cannot be lazy.
+Laziness only applies to lines that would have been continuations of
+paragraphs had they been prepended with `>`. For example, the
+`>` cannot be omitted in the second line of
+
+``` markdown
+> foo
+> ---
+```
+
+without changing the meaning:
.
> foo
@@ -2349,6 +2356,15 @@ block structure cannot be lazy.
<hr />
.
+Similarly, if we omit the `>` in the second line of
+
+``` markdown
+> - foo
+> - bar
+```
+
+then the block quote ends after the first line:
+
.
> - foo
- bar
@@ -2363,6 +2379,9 @@ block structure cannot be lazy.
</ul>
.
+For the same reason, we can't omit the `>` in front of
+subsequent lines of an indented or fenced code block:
+
.
> foo
bar