- Commit
- 74d46d8b243d59358a806357cfba706abfa72aa1
- Parent
- 42cd5230d423f20f9367754975d10f6ddf4c0430
- Author
- John MacFarlane <jgm@berkeley.edu>
- Date
Update spec.txt.
My personal build of CMark ✏️
Update spec.txt.
1 file changed, 14 insertions, 2 deletions
Status | File Name | N° Changes | Insertions | Deletions |
Modified | test/spec.txt | 16 | 14 | 2 |
diff --git 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