From 260b808152e125ba80483c206bd693e4bceb8129 Mon Sep 17 00:00:00 2001
From: Michael Howell for a truly equivalent line, we need to remove spaces
+
+````````````````````````````````
+
```````````````````````````````` example
-→→foo
.
@@ -3689,11 +3713,12 @@ these constructions. (A recipe is provided below in the section entitled
## Block quotes
-A [block quote marker](@),
-optionally preceded by up to three spaces of indentation,
-consists of (a) the character `>` together with a following space of
-indentation, or (b) a single character `>` not followed by a space of
-indentation.
+A [block quote marker](@) is either complete or incomplete.
+A [complete block quote marker](@) consists of the character `>` together with
+a following space of indentation.
+An [incomplete block quote marker](@) consists of the character `>`, and
+cannot have a space or a tab after it.
+Any block quote marker may be preceded by up to three spaces of indentation.
The following rules define [block quotes]:
@@ -3702,6 +3727,16 @@ The following rules define [block quotes]:
marker] to the beginning of each line in *Ls*
is a [block quote](#block-quotes) containing *Bs*.
+ To prepend a [complete block quote marker] to a line, calculate its
+ indentation without the list marker at the current tab stop (N1),
+ then insert `>` at the start of the line, then calculate its indentation at
+ the same tab stop (N2, which will equal N1 unless the line starts with a tab),
+ then add M=N1+1-N2 spaces of indentation (if M is negative, remove spaces).
+
+ An [incomplete block quote marker] can be be used instead, but
+ only if the line does not start with a space or tab. A single block quote
+ container can use a mix of both marker styles.
+
2. **Laziness.** If a string of lines *Ls* constitute a [block
quote](#block-quotes) with contents *Bs*, then the result of deleting
the initial [block quote marker] from one or
@@ -4095,15 +4130,20 @@ baz
+
+
+ if we just add a caret, we bump to the next tab stop and have six (but the quote eats one, so it's five)
+
+
+
code @@ -4112,6 +4152,15 @@ after the `>`:
+not code
+```````````````````````````````` From 0dcc1c3f735a64d71bff6a44c9d4fbeb56062dfc Mon Sep 17 00:00:00 2001 From: Michael Howell+
+- +
+first paragraph in list item using an incomplete block quote marker
+the second paragraph must use a complete block quote marker
+not the third paragraph
+Date: Wed, 5 Feb 2025 09:22:47 -0700 Subject: [PATCH 2/2] Clean up some incorrect language now that I slept on it Thanks, woorm, for catching that "list marker" mistake. --- spec.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec.txt b/spec.txt index 9cc86a04..abcb1246 100644 --- a/spec.txt +++ b/spec.txt @@ -3728,9 +3728,9 @@ The following rules define [block quotes]: is a [block quote](#block-quotes) containing *Bs*. To prepend a [complete block quote marker] to a line, calculate its - indentation without the list marker at the current tab stop (N1), + indentation without the block quote marker at the current column (N1), then insert `>` at the start of the line, then calculate its indentation at - the same tab stop (N2, which will equal N1 unless the line starts with a tab), + the same column (N2, which will equal N1 unless the line starts with a tab), then add M=N1+1-N2 spaces of indentation (if M is negative, remove spaces). An [incomplete block quote marker] can be be used instead, but