diff options
author | John MacFarlane <jgm@berkeley.edu> | 2014-12-13 22:35:13 -0800 |
---|---|---|
committer | John MacFarlane <jgm@berkeley.edu> | 2014-12-13 22:35:13 -0800 |
commit | 6df2047d90d81e6269a37e7e6843211edf4ba3c6 (patch) | |
tree | d4e4a110b920e8d9cc12a8bb10c38215cabb9b67 /spec.txt | |
parent | 5d07c293d6fa169d665dc4e1ea3cea4271d92ccc (diff) |
Clarified spec on indented code blocks.
Previously the spec said, wrongly, that a blank line was needed
between a paragraph and a following code block. It is only needed
between a code block and a following paragraph (due to lazy
continuations).
Thanks to textnut for pointing this out.
Diffstat (limited to 'spec.txt')
-rw-r--r-- | spec.txt | 15 |
1 files changed, 8 insertions, 7 deletions
@@ -948,18 +948,19 @@ use backslash escapes: ## Indented code blocks -An [indented code block](@indented-code-block) -is composed of one or more +An [indented code block](@indented-code-block) is composed of one or more [indented chunks](#indented-chunk) separated by blank lines. -An [indented chunk](@indented-chunk) -is a sequence of non-blank lines, each indented four or more -spaces. An indented code block cannot interrupt a paragraph, so -if it occurs before or after a paragraph, there must be an -intervening blank line. The contents of the code block are +An [indented chunk](@indented-chunk) is a sequence of non-blank lines, +each indented four or more spaces. The contents of the code block are the literal contents of the lines, including trailing newlines, minus four spaces of indentation. An indented code block has no attributes. +An indented code block cannot interrupt a paragraph, so there must be +a blank line between a paragraph and a following indented code block. +(A blank line is not needed, however, between a code block and a following +paragraph.) + . a simple indented code block |