Chris Sewell

> is this "Markdown centric" way documented in - https://myst-parser--717.org.readthedocs.build/en/717/syntax/typography.html#inline-text-formatting - https://myst-parser--717.org.readthedocs.build/en/717/syntax/code_and_apis.html#inline-syntax-highlighting Feedback welcome though > (BTW, thanks for working so hard on a new release!) Thanks!

Hey @adam-grant-hendry I'm not sure what you mean here; you can use any extension alongside `myst-parser`, as indeed is the case for the building of the documentation here: https://github.com/executablebooks/MyST-Parser/blob/28725fceb8e1e117cb247b06a267f82c501ce527/docs/conf.py#L28 Is...

This is not something I'm really willing to add: the fact that myst-parser uses markdown-it-py is really an implementation detail that is not exposed to the user: 1. This implementation...

Obviously, if you have ideas for new/improved syntaxes, then I welcome issues here, and also in https://github.com/executablebooks/myst-spec / https://github.com/executablebooks/myst-enhancement-proposals

> just FYI, '.py' is a tld. And shouldn't this be an issue at linkify-it-py and not here? I would raise this with linkify-it-py Happy to consider adding "configurability" for...

> It should be easy to use myst_parser programmatically with sphinx extensions. Hey @paugier I'm afraid this is just not really possible, since sphinx does not expose an API that...

As discussed with @giovannipizzi (who suggested it)

as discussed with @giovannipizzi

yep that would be cool as well 👍 However, we can capture the full information about a code, profile, etc in the YAML

As mentioned, this is working with https://github.com/aiidateam/aiida-firecrest