-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown footnotes are not wrapped correctly #188
Labels
Comments
Problem the same as #63 |
Closing as duplicate of #63. I did try to fix it but found I basically had to rewrite the markdown parser to fix that (and other) bugs, which is still a WIP |
stkb
added a commit
that referenced
this issue
Nov 29, 2021
stkb
added a commit
that referenced
this issue
Dec 19, 2021
stkb
added a commit
that referenced
this issue
Jan 14, 2022
- New architecture (still WIP) with performance increase. - Markdown: new parser that fixes many small bugs (inc #288), as well as supporting: - Front matter header (#277, #294) - Link reference definitions (#63, #93) - Footnotes (#188) - ReStructuredText support (standalone & for Python, almost complete) (#88). - Julia: support `#= ... =#` block comments (#302) - Visual Studio: Wrap to rulers generated from .editorconfig by the Editor Guidelines extension (thereby indirectly supporting .editorconfig) (#300).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, an overlong footnote like so:
is not rewrapped, violating an 80 character limit. Manually rewrapping to
which follows guidelines for long footnotes, is incorrectly rewrapped to
which is rendered as an empty footnotes and places an unwanted paragraph in the main text.
I would be able to work around this bug by simply allowing long-lined footnotes if I only had simple footnotes, but unfortunately more complicated footnotes, like this one from the footnote documentation above, are always mangled by rewrap.
Would it be possible to add support for long footnotes and fix this bug? Thank you.
The text was updated successfully, but these errors were encountered: