Skip to content

Commit

Permalink
Block quote marker choice uniformity
Browse files Browse the repository at this point in the history
Require that the same block quote marker be used to avoid ambiguity in parsing strategy (compatible with the algorithm described [here](commonmark#460 (comment)))
  • Loading branch information
aidantwoods authored Apr 27, 2017
1 parent f1d14f2 commit ed90fbe
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions spec.txt
Original file line number Diff line number Diff line change
Expand Up @@ -3194,9 +3194,12 @@ with a following space, or (b) a single character `>` not followed by a space.
The following rules define [block quotes]:

1. **Basic case.** If a string of lines *Ls* constitute a sequence
of blocks *Bs*, then the result of prepending a [block quote
of blocks *Bs*, then the result of prepending the same [block quote
marker] to the beginning of each line in *Ls*
is a [block quote](#block-quotes) containing *Bs*.
is a [block quote](#block-quotes) containing *Bs*. If some lines in *Ls*
are blank lines, then trailing whitespace after a block quote marker
may be omitted without affecting the interpertation of which block quote
marker was prepended.

2. **Laziness.** If a string of lines *Ls* constitute a [block
quote](#block-quotes) with contents *Bs*, then the result of deleting
Expand Down

0 comments on commit ed90fbe

Please sign in to comment.