emacs/var/elfeed/db/data/cf/cfdde15c4c51bc728667a5ac09eef1ad90beb78f
2022-01-03 12:49:32 -06:00

1 line
1.9 KiB
Plaintext

<!-- SC_OFF --><div class="md"><p>I arrange my orgmode notes as single files with lots of entries. This works great for me because emacs is more buffer-oriented than directory-oriented, so all the emacs search commands optimize for single-file approaches (eg search all headlines in my tech/blog file for the keyword of that Linux function I&#39;ve forgotten how to use).</p> <p>The single problem I have is footnotes. From the documentation you have two options: inline or in a file-wide section. My footnotes are often too long to fit inline, so I can change the name of that section but CANNOT make a section-per-entry arrangement, which is what I really want. The way I have worked around this with my blog is to always have the entry I am publishing at the top of the file, so using <code>org-footnote-new</code> finds that entries footnote section first and inserts things where I want them to be. I&#39;ve used this compromise successfully for quite some time, but it depends on the fact that you are not going to add footnotes to anything but the top entry.</p> <p>Now I am converting footnotes in a non-orgmode date made by someone else, and moving the elements to the top of the file is not an option. Does anyone know of a way of implementing an entry-by-entry footnote section (say, for every * entry, or every ** entry as the case may be) without moving the single entry to the top of the buffer? The goal is for each entry to have a working footnote section of its own, which works nicely with <code>org-footnote-action</code>.</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/WorldsEndless"> /u/WorldsEndless </a> <br/> <span><a href="https://www.reddit.com/r/orgmode/comments/q7bpwc/how_to_have_orgmode_footnotes_per_entry/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/orgmode/comments/q7bpwc/how_to_have_orgmode_footnotes_per_entry/">[comments]</a></span>