diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2014-10-26 00:26:38 -0700 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2014-10-26 00:26:38 -0700 |
| commit | 15422f68253bd5d877f0b308b1bf6caec6e0eb79 (patch) | |
| tree | 400f25cc5753c0fd538da6bdae2c45d3d4691c50 | |
| parent | 198d93379594ef80081f2cbd0e6e792cec683f2e (diff) | |
Tweaked the closing fence section added in last commit.
| -rw-r--r-- | spec.txt | 46 |
1 files changed, 15 insertions, 31 deletions
@@ -1288,45 +1288,41 @@ aaa </code></pre> . -Closing fences may be indented by 0-3 spaces: +Four spaces indentation produces an indented code block: . -``` -code -``` -. -<pre><code>code -</code></pre> -. - + ``` + aaa + ``` . +<pre><code>``` +aaa ``` -code - ``` -. -<pre><code>code </code></pre> . +Closing fences may be indented by 0-3 spaces, and their indentation +need not match that of the opening fence: + . ``` -code +aaa ``` . -<pre><code>code +<pre><code>aaa </code></pre> . . -``` -code ``` +aaa + ``` . -<pre><code>code +<pre><code>aaa </code></pre> . -But not by 4: +This is not a closing fence, because it is indented 4 spaces: . ``` @@ -1338,18 +1334,6 @@ aaa </code></pre> . -Four spaces indentation produces an indented code block: - -. - ``` - aaa - ``` -. -<pre><code>``` -aaa -``` -</code></pre> -. Code fences (opening and closing) cannot contain internal spaces: |