summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2018-10-04 15:40:26 -0700
committerJohn MacFarlane <jgm@berkeley.edu>2018-10-04 15:40:26 -0700
commit74d46d8b243d59358a806357cfba706abfa72aa1 (patch)
tree211d746cc771d743d98b231b6a1d5d2b11b6f0f8 /test
parent42cd5230d423f20f9367754975d10f6ddf4c0430 (diff)
Update spec.txt.
Diffstat (limited to 'test')
-rw-r--r--test/spec.txt16
1 files changed, 14 insertions, 2 deletions
diff --git a/test/spec.txt b/test/spec.txt
index bd2affb..d24a923 100644
--- a/test/spec.txt
+++ b/test/spec.txt
@@ -1584,8 +1584,8 @@ begins with a code fence, indented no more than three spaces.
The line with the opening code fence may optionally contain some text
following the code fence; this is trimmed of leading and trailing
-whitespace and called the [info string](@).
-The [info string] may not contain any backtick
+whitespace and called the [info string](@). If the [info string] comes
+after a backtick fence, it may not contain any backtick
characters. (The reason for this restriction is that otherwise
some inline code would be incorrectly interpreted as the
beginning of a fenced code block.)
@@ -1973,6 +1973,18 @@ foo</p>
````````````````````````````````
+[Info strings] for tilde code blocks can contain backticks and tildes:
+
+```````````````````````````````` example
+~~~ aa ``` ~~~
+foo
+~~~
+.
+<pre><code class="language-aa">foo
+</code></pre>
+````````````````````````````````
+
+
Closing code fences cannot have [info strings]:
```````````````````````````````` example