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
Marktext should not move footnotes contents to the real end of document #2036
Comments
Thank you for taking the time to report this issue. @Jocs Could you please explain, why we put the footnotes that the end of the document and whether it's possible to keep the old position. |
According pandoc document
At the time of development, it placed at the end of document according to the usual habits, or my personal habits, I did not consider it too much, this will be optimized in the future. |
@N0rbert out of curiosity, does Mark Text display |
@gilbertohasnofb my main gold standard here is retext. The PDF and HTML exports from MarkText v0.16.2 looks the same. But footnote is still moved to the end of document on save. |
Strangely enough, footnotes do not seem to work on my Linux Mintt 18.3 installation and MarkText 0.16.2. Pasting your minimal example in source code mode: Going back into regular mode, I see: So:
|
@gilbertohasnofb this behaviour may be caused by disabled Markdown Extensions (i.e. Use pandoc-style footnotes) in the Preferences. Below is what I have set: Then after restart I the following: |
That was it, I did not know that this was not enabled by default. Now I can reproduce your issue and the output looks exactly like the last screenshot. |
Still not fixed in 0.16.3. |
Description
Using MarkText with version control system become difficult because of moving footnotes to the real end of document.
Steps to reproduce
Have Markdown document with footnotes defined
Open the document using MarkText
Save the document
Expected behavior:
the MarkText does not change the document
Actual behavior:
the MarkText changed the document, moved footnote to the real end of the document:
Versions
The text was updated successfully, but these errors were encountered: