MichaBrugger / obsidian-footnotes

Makes creating footnotes in Obsidian more fun!
119 stars 13 forks source link

FR: footnote number prefix... #31

Open olearydj opened 8 months ago

olearydj commented 8 months ago

Hello and thanks for this handy plugin!

I often use Obsidian to work in large documents that are split into "chapters," each with their own MD file. The combined document is a skeleton that embeds the chapters. When I'm ready to publish the combined document I use the easy bake plugin to create a single MD that I export as PDF, or I use the enhancing export to directly generate DOC, PDF, etc.

Footnotes with conflicting numbers present a bit of a problem in this scenario, e.g. footnote #1 in chapter 2 and footnote #1 in chapter 4. What I end up doing is prefixing the numbered notes with the chapter number, e.g. [^2.1]. This works, but isn't supported by your plugin.

It would be nice if we could define a prefix in the metadata, e.g. foot-pfx: 1. that is used when generating the numbered footnotes.

Thanks for your consideration and for sharing this plugin.

Comprehensive-Jason commented 8 months ago

I see. The Longform plugin, which serves a similar function to the Easy Bake plugin but with more features, has an open issue around renumbering conflicting footnotes.

In the meantime, I can definitely try adding this as an optional feature in settings. To be clear, you want the prefix number to be read from Obsidian properties like so?: image

While you wait for the fix, you can always manually number the footnotes using the Insert/Navigate Named Footnote command. See here in the README if you need help.

olearydj commented 8 months ago

Thanks very much! I've used Longform, and have it installed, but find it overly complicated for what it does / I need in Obsidian.

Yes, read from the properties. I'm using insert named now, as you suggested.

mk-uc commented 1 month ago

A quick +1 for this and a suggestion: rather than using a properties field, why not just automatically prefix the footnote with the current time in seconds, so you end up with something like 1721228902-1. This is what Brett Terpstra does in his Markdown tools. Not the prettiest, but definitely effective