summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2014-10-26 00:18:05 -0700
committerJohn MacFarlane <jgm@berkeley.edu>2014-10-26 00:18:05 -0700
commit198d93379594ef80081f2cbd0e6e792cec683f2e (patch)
treeeee0d182b6f077b2d5c6e3801e53e27dd954aec1
parentb964cd14c1574388e805c2b173d21ba5c43cbe42 (diff)
parentadfa8750cd771688156e0f386b980f9214c4063b (diff)
Merge pull request #116 from Bengt/code_block_closing_fences
Add example from issue #94 about indented code block closing fences
-rw-r--r--spec.txt52
1 files changed, 50 insertions, 2 deletions
diff --git a/spec.txt b/spec.txt
index 12ec482..c226866 100644
--- a/spec.txt
+++ b/spec.txt
@@ -1288,6 +1288,56 @@ aaa
</code></pre>
.
+Closing fences may be indented by 0-3 spaces:
+
+.
+```
+code
+```
+.
+<pre><code>code
+</code></pre>
+.
+
+.
+```
+code
+ ```
+.
+<pre><code>code
+</code></pre>
+.
+
+.
+```
+code
+ ```
+.
+<pre><code>code
+</code></pre>
+.
+
+.
+```
+code
+ ```
+.
+<pre><code>code
+</code></pre>
+.
+
+But not by 4:
+
+.
+```
+aaa
+ ```
+.
+<pre><code>aaa
+ ```
+</code></pre>
+.
+
Four spaces indentation produces an indented code block:
.
@@ -6440,5 +6490,3 @@ an `emph`.
The document can be rendered as HTML, or in any other format, given
an appropriate renderer.
-
-