You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2021. It is now read-only.
Running the markdown command against a file containing the sample footnotes markdown from the Pandoc documentation that looks like this:
Here is a footnote reference,[^1] and another.[^longnote]
[^1]: Here is the footnote.
[^longnote]: Here's one with multiple blocks.
Subsequent paragraphs are indented to show that they
belong to the previous footnote.
{ some.code }
The whole paragraph can be indented, or just the first
line. In this way, multi-paragraph footnotes work like
multi-paragraph list items.
This paragraph won't be part of the note, because it
isn't indented.
...results in the the content of the footnote being omitted entirely.
I followed this issue back in time via git-bisect, which told me, f721084df01b8847314a38c97bb723bf4e5d9dee is the first bad commit. I wish I were smart enough to come up with a patch.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this bug. It was introduced with revision cca2b1a, an optimization
that does not work with footnotes.
I'm working on a fix (which still may take a while), a workaround is to comment out the lines
84: savedPos := p.yy.state.heap.Pos()
and line
94: p.yy.state.heap.setPos(savedPos)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Running the
markdown
command against a file containing the sample footnotes markdown from the Pandoc documentation that looks like this:...results in the the content of the footnote being omitted entirely.
I followed this issue back in time via git-bisect, which told me,
f721084df01b8847314a38c97bb723bf4e5d9dee is the first bad commit
. I wish I were smart enough to come up with a patch.The text was updated successfully, but these errors were encountered: