Chris Sewell

Thanks @cpitclaudel this requires fixes for a number of the regression tests (if you didn't know you can run `pytest --force-regen` My question would be though; should the behaviour be...

I think there is some confusion is some of the later comments, conflating the use of `.html` and `.md` extensions: `myst_heading_anchors` only work for `.md` extensions, i.e. `[text](page.md#something)` will link...

yes indeed this is not a feature currently supported by myst-parser, and not something planned. PRs are welcome though

Heya, yeh cheers it should be quite easy to add to https://github.com/executablebooks/MyST-Parser/blob/be4838c35d374a51427a92a2736b29a9abc018d4/myst_parser/main.py#L31

Heya, yep the Markdown fence is just handled as a special case of the `code-block` directive (i.e. with no options allowed). Happy to receive PRs to improve the documentation 😄

Hey @LuisBL, from https://github.com/mgaitan/sphinxcontrib-mermaid, `mermaid` is a directive (not a code-block) so you have use it with braces ```` ```{mermaid} graph LR a --> b ``` ```` I'm a little...

> Sorry my issue was not clear/compleat, updated. Cheers, but what happens now if you add? ```` ```{mermaid} graph LR a --> b ``` ```` (with `extensions = [ 'myst_parser',...

> so I can close this and open an issue to improve the documentation with the above exemple. brilliant 😄

FYI, If you want to show nested code blocks you can just use more surrounding `` ` `` ````` ```` ```{mermaid} graph LR a --> b ``` ```` `````

> syntax has the advantage that is render with the gitlab.com markdown renderer You can always use: ```` ```{eval-rst} .. mermaid:: graph LR a --> b ``` ```` that would...