From 6df2047d90d81e6269a37e7e6843211edf4ba3c6 Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Sat, 13 Dec 2014 22:35:13 -0800 Subject: 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. --- spec.txt | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/spec.txt b/spec.txt index c1b2e88..b6d4e51 100644 --- a/spec.txt +++ b/spec.txt @@ -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 -- cgit v1.2.3