From e70a8222d05f33efe07881ea4102cf4952165eb7 Mon Sep 17 00:00:00 2001
From: John MacFarlane <jgm@berkeley.edu>
Date: Sat, 25 Jul 2015 21:51:43 -0700
Subject: Added test case clarifying laziness in block quotes.

See jgm/commonmark.js#60.
---
 spec.txt | 32 ++++++++++++++++++++++++++++----
 1 file changed, 28 insertions(+), 4 deletions(-)

(limited to 'spec.txt')

diff --git a/spec.txt b/spec.txt
index ef645e7..3aa4ee4 100644
--- a/spec.txt
+++ b/spec.txt
@@ -2835,8 +2835,8 @@ foo</p>
 .
 
 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
+paragraphs had they been prepended with [block quote marker]s.
+For example, the `> ` cannot be omitted in the second line of
 
 ``` markdown
 > foo
@@ -2855,7 +2855,7 @@ without changing the meaning:
 <hr />
 .
 
-Similarly, if we omit the `>` in the second line of
+Similarly, if we omit the `> ` in the second line of
 
 ``` markdown
 > - foo
@@ -2878,7 +2878,7 @@ then the block quote ends after the first line:
 </ul>
 .
 
-For the same reason, we can't omit the `>` in front of
+For the same reason, we can't omit the `> ` in front of
 subsequent lines of an indented or fenced code block:
 
 .
@@ -2905,6 +2905,30 @@ foo
 <pre><code></code></pre>
 .
 
+Note that in the following case, we have a paragraph
+continuation line:
+
+.
+> foo
+    - bar
+.
+<blockquote>
+<p>foo
+- bar</p>
+</blockquote>
+.
+
+To see why, note that in
+
+```markdown
+> foo
+>     - bar
+```
+
+the `- bar` is indented too far to start a list, and can't
+be an indented code block because indented code blocks cannot
+interrupt paragraphs, so it is a [paragraph continuation line].
+
 A block quote can be empty:
 
 .
-- 
cgit v1.2.3