From: James Harkins <jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bad footnotes when including org files
Date: Sun, 16 Mar 2014 01:32:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20140316T021911-415@post.gmane.org> (raw)
In-Reply-To: 5324E5F1.5080207@gmail.com
Xavier Garrido <xavier.garrido <at> gmail.com> writes:
>
> Hi Orgers,
>
> I am having some troubles with several org files that I want to include
> into one general org file. To do that I use the #+INCLUDE: keywords and
> actually, everything is working well until I add some footnotes in both
> files. Let me show you a minimal example where the footnote numbering is
> getting weird
>
> When I export to LaTeX the latest file, I get two footnotes with the
> same number. The problem can be solved by changing the label of the
> second footnote to [fn:2] but it means that I have to reorganize and
> reorder footnotes within all the org files I will include. I am
> wondering if it is possible to run, for example,
> =org-footnote-renumber-fn:N= function when including files in such way
> the user will not have to take care footnote labels.
I had exactly this problem in a big project. Poking around the customization
group org-footnote, I found:
Org Footnote Auto Label: Value Menu Create a random label
State: SAVED and set.
Non-nil means define automatically new labels for footnotes.
Possible values are:
nil Prompt the user for each label.
t Create unique labels of the form [fn:1], [fn:2], etc.
confirm Like t, but let the user edit the created value.
The label can be removed from the minibuffer to create
an anonymous footnote.
random Automatically generate a unique, random label.
plain Automatically create plain number labels like [1].
I switched to random labels, and no problem since then.
I don't find any evidence of a function that will automatically switch
existing footnotes to random IDs, though, and I'm afraid I'm short of time
this morning. It should be possible, but I guess nobody has done it.
But, do set the custom var to use random labels. It will prevent the problem
for all new footnotes.
hjh
next prev parent reply other threads:[~2014-03-16 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 23:44 Bad footnotes when including org files Xavier Garrido
2014-03-16 1:32 ` James Harkins [this message]
2014-03-16 17:29 ` Xavier Garrido
2014-03-26 14:41 ` Nicolas Goaziou
2014-03-26 20:34 ` Xavier Garrido
2014-04-12 13:10 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20140316T021911-415@post.gmane.org \
--to=jamshark70@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).