diff options
author | Jay Weisskopf <jay@jayschwa.net> | 2019-08-05 13:07:20 -0400 |
---|---|---|
committer | John MacFarlane <jgm@berkeley.edu> | 2019-08-05 10:07:20 -0700 |
commit | 8b768f7701d22357815c36abf4b04d7616357e17 (patch) | |
tree | e68c3821ade2a5a3af216d29a8588bbadc1f3c3c | |
parent | 3991f0557687a2a7bb89bc7ce971918064bb1fc9 (diff) |
Clarify that new blocks are added to *container* blocks. (#598)
My first attempt at writing a parser added new blocks to the last
matched block, regardless if it was a container or leaf. I think it
would have helped me if it had explicitly said "container" here.
-rw-r--r-- | spec.txt | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -9443,7 +9443,7 @@ blocks. But we cannot close unmatched blocks yet, because we may have a blocks, we look for new block starts (e.g. `>` for a block quote). If we encounter a new block start, we close any blocks unmatched in step 1 before creating the new block as a child of the last -matched block. +matched container block. 3. Finally, we look at the remainder of the line (after block markers like `>`, list markers, and indentation have been consumed). |