Rendering Footnotes

[stoweboyd]

It would be good if footnotes were rendered in the copied file.

In my use case, I write comments and place tags and other annotations in footnotes, but for sharing with others those would be better at the foot of the rendered file.

[mcndt]

I agree, footnotes should be rendered correctly. I'll mark it as a future feature. Stay tuned!

[mcndt]

for future reference, a good starting point: markedjs/marked#1562 (comment)

[mcndt]

Works now!

[stoweboyd]

Doesn't seem to work in all cases: see https://noteshare.space/note/cl76nu7jj339101nuogo2pdp5#7BwC5OXgRneeFoalJM3GH6r-4iGTvVD7mVjW6w1HjtQ

[mcndt]

So sorry for my late response, I have been traveling.

I am unfamiliar with this footnote syntax. Is it a way to define the footnote text inline? I was previously only familiar with this syntax:

This is a paragraph^[1].

[1]: This is the footnote text, which will be rendered at the bottom of the page.

[stoweboyd]

Yes, it is an inline footnote. Like^[this is a footnote] which shows at the foot of the rendered file with an ordinal and the text. See https://help.obsidian.md/How+to/Format+your+notes You can also use inline footnotes. ^[notice that the carat goes outside of the brackets on this one.]

…

On Fri, Sep 9, 2022 at 4:53 PM Maxime Cannoodt ***@***.***> wrote: So sorry for my late response, I have been traveling. I am unfamiliar with this footnote syntax. Is it a way to define the footnote text inline? I was previously only familiar with this syntax: This is a paragraph^[1]. [1]: This is the footnote text, which will be rendered at the bottom of the page. — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFR3XNZE4KQCMY5H4SLLDV5OPTFANCNFSM57IF3PZA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mcndt]

I created a new issue to track this bug separately, see #31.

[stoweboyd]

Still doesn't seem to be working?

…

On Sun, Sep 11, 2022 at 5:28 AM Maxime Cannoodt ***@***.***> wrote: Closed #24 <#24> as completed. — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFR3U6KNJ7UTXATC3KXR3V5WQ43ANCNFSM57IF3PZA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mcndt]

As I said, I created a new issue to track the bug. I haven't fixed it just yet :) But don't worry, it's on my radar.

You can subscribe to the new thread to follow progress: #31

[stoweboyd]

Aha!

…

On Sun, Sep 11, 2022 at 2:57 PM Maxime Cannoodt ***@***.***> wrote: As I said, I created a new issue to track the bug. I haven't fixed it just yet :) But don't worry, it's on my radar. You can subscribe to the new thread to follow progress: #31 <#31> — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFR3V53FSHNMEZK42LJVTV5YTRRANCNFSM57IF3PZA> . You are receiving this because you authored the thread.Message ID: ***@***.***>