Originally posted by @chrisjsewell in #18 (comment)
Thanks @CodeCox.
I have to say, I have not touched this project in months (although I do use it daily within VS Code for the syntax highlighting).
Since then, there has been many, many changes to myst; notably (since vs-code uses markdown-it) the creation of markdown-it-py as the backend to myst-parser, the addition of extended support for a number of markdown-it plugins, and the creation of markdown-it-myst.
I hope to circle back around to this project then (when time permits!), to re-appraise it and integrate all these new developments in.
Ling story short, this should fix the bug!
Originally posted by @chrisjsewell in #18 (comment)
Thanks @CodeCox.
I have to say, I have not touched this project in months (although I do use it daily within VS Code for the syntax highlighting).
Since then, there has been many, many changes to myst; notably (since vs-code uses markdown-it) the creation of markdown-it-py as the backend to myst-parser, the addition of extended support for a number of markdown-it plugins, and the creation of markdown-it-myst.
I hope to circle back around to this project then (when time permits!), to re-appraise it and integrate all these new developments in.
Ling story short, this should fix the bug!