Chris Sewell

Yep sounds reasonable; I have done something similar with tables in latex. Ideally what I think you would want here is a "scoped" footnote section, i.e. at the bottom of...

I think it sounds reasonable 👍

Heya, Perhaps @tsutsu3 (as the maintainer of linkify-it-py) and @hukkin would like to comment?

thanks, I'll have to think about this one, perhaps as part of the `include` directive there could be an option to set the initial header level

No this warning arises directly from MyST-Parser: https://github.com/executablebooks/MyST-Parser/blob/4e02629f5fb575fdd733ca43891bebb2e312ad00/myst_parser/docutils_renderer.py#L258-L266 correctly, because for example ```md # title ## sub-title ``` ```md # title ### sub-title ``` ```md ## title ### sub-title ```...

With https://github.com/executablebooks/MyST-Parser/pull/313, this warning can now be suppressed. I will leave this issue open though, as for `include` it would probably be better to have an extra option to "add/minus...

(@choldgraf you beat me to it) Heya @luizirber, could you expand on "link to". Do you mean show images from this folder? If so then IRC you could use ``,...

> and thanks again for taking time to answer, because I realise it is not necessarily a MyST-related issue Oh no I can definitely see the use case 👍 >...

Yeh good idea thanks. I wonder if we can essentially write a new markdown-it-py renderer (a bit like https://github.com/executablebooks/mdformat) that outputs the requisite pygments tokens, and have pygments recognise this...

Heya, I'd note there is some "wider" efforts currently going on, around specifying MyST: https://github.com/executablebooks/myst-spec Really, the goal is to not have it directly tied to sphinx/docutils, e.g. this is...