From 5976351c4da21f429648abf986954ad45c9fbcd7 Mon Sep 17 00:00:00 2001
From: John MacFarlane <jgm@berkeley.edu>
Date: Mon, 8 Jun 2015 11:00:25 -0700
Subject: Clarified lazy block quote examples.  (Closes #328.)

---
 changelog.txt |  9 +++++----
 spec.txt      | 25 ++++++++++++++++++++++---
 2 files changed, 27 insertions(+), 7 deletions(-)

diff --git a/changelog.txt b/changelog.txt
index 4ebb662..3199637 100644
--- a/changelog.txt
+++ b/changelog.txt
@@ -2,17 +2,18 @@
 
   * Require at least one nonspace character in a link label (#322).
   * Require replacement (rather than omission) of U+0000 (#327).
-  * Clarify that entities resolving to U+0000 are to be
+  * Clarified that entities resolving to U+0000 are to be
     replaced by U+FFFD (#323).
   * Removed statement that what counts as a line ending is
     platform-dependent (#326).  We now count `\r`, `\n`,
     or `\r\n` as a line ending regardless of the platform.
     (The line ending styles can even be mixed in a single document.)
-  * Define "space."
-  * Revise "non-space character". Previously a non-space character
+  * Defined "space."
+  * Revised "non-space character". Previously a non-space character
     was defined as anything but a space (U+0020).  Now it is anything
     that is not a whitespace character (as defined in the spec).
-  * Clarify that tab expansion is a preprocessing step (#330).
+  * Clarified that tab expansion is a preprocessing step (#330).
+  * Clarified lazy block quote examples (#328).
   * Added a test case with `#` directly followed by a letter
     (not an ATX header).
   * Added two test cases illustrating that a list at the
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
-- 
cgit v1.2.3