Open agoose77 opened 1 year ago
This is potentially going to be tricky. Right now we parse markdown in a per-block basis to speed things up a bit. Currently the footnote reference is resolved by the tokenizer (markdown-it), not the AST, which means if it isn't found the reference is interpreted as text, and we can't resolve it later.
There are a few options:
If we want the feature, I think that (1) would be the way to go.
Any plan to fix this?
Here's is how I used jupyterlab-myst:
I'm using vscode extension "Markdown Footnotes" (by Matt Bierner), and it will create footnotes definition at the end of the markdown file, and finally break.
Another question, even I managed to put the definition and link into one cell, the definition will just showed as tooltip. Is this by design? Would it be possible to show the definition always at the end of the cell/notebook?
Describe the bug
context When I add a footnote with
some sentence [^footnote]
and[^footenote]: ...
expectation I expected a wild footnote to appear
bug But instead the raw footnote markup is rendered.
Reproduce the bug
List your environment
No response