-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The fenced code attribute context renderers are only produced when the For example, assume that you have the following Markdown document ~~~~ {#mycode .haskell .numberLines startFrom=100}
qsort [] = []
qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++
qsort (filter (>= x) xs)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Processing the document $ markdown-cli fencedCodeAttributes=true example.md \markdownRendererDocumentBegin
\markdownRendererFencedCodeAttributeContextBegin\markdownRendererAttributeIdentifier{mycode}\markdownRendererAttributeClassName{haskell}\markdownRendererAttributeClassName{numberLines}\markdownRendererAttributeKeyValue{startFrom}{100}\markdownRendererInputFencedCode{./6c80369efc4b7e2154ad1c5b0019af21.verbatim}{}{}\markdownRendererFencedCodeAttributeContextEnd{}\markdownRendererDocumentEnd Unless you wish to use HTML attributes, I would redefine P.S.: In the future, please address questions that aren't bug reports to https://github.com/Witiko/markdown/discussions. |
Beta Was this translation helpful? Give feedback.
The fenced code attribute context renderers are only produced when the
fencedCodeAttributes
option has been enabled and there are HTML attributes attached to a fenced code block.For example, assume that you have the following Markdown document
example.md
: