From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leonard Randall Subject: Moving footnotes Date: Wed, 21 May 2014 13:23:19 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c339e6c5b9e504f9e80f39 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45940) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wn5YH-0003bW-4L for emacs-orgmode@gnu.org; Wed, 21 May 2014 08:23:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wn5YG-0001c0-6p for emacs-orgmode@gnu.org; Wed, 21 May 2014 08:23:21 -0400 Received: from mail-oa0-x231.google.com ([2607:f8b0:4003:c02::231]:47895) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wn5YG-0001b3-1d for emacs-orgmode@gnu.org; Wed, 21 May 2014 08:23:20 -0400 Received: by mail-oa0-f49.google.com with SMTP id eb12so2089904oac.8 for ; Wed, 21 May 2014 05:23:19 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode --001a11c339e6c5b9e504f9e80f39 Content-Type: text/plain; charset=UTF-8 Hi all, One of the things I really like about org-mode is the ability to quickly move material between projects. For instance, I sometimes write material as a conference paper and want to use some sections in my thesis. I also like to keep a file with old chapter drafts for later reference (I could just use git for this, but keeping an old-drafts file around makes some jobs more convenient). One issue that I am running into is that when I move material with org-refile, footnotes defined in the Footnote section do not move with it. Additionally, if I try to export a subtree as an org buffer, it does not take footnote definitions with it. The obvious workaround for both problems is to define footnotes inline. Another option (the one that I am using currently) is to set org-footnote-section to nil, and to set org-footnote-auto-label to 'random. This way footnotes are kept at the bottom of the section, so they move with refile, and they have randomly generated names, so they won't conflict with any footnote definitions in the destination file. This solution works, but I wondered if there was any way to get org-refile and org-export-org to take footnotes definitions with them, wherever they are located. With org-export-org, this seems especially important as backends are supposed to faithfully export footnotes with their definitions. Additionally, is there a way to easily convert numbered footnotes to randomly named footnotes? Thanks, Leonard --001a11c339e6c5b9e504f9e80f39 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,
One of the things I really like= about org-mode is the ability to quickly move material between projects. F= or instance, I sometimes write material as a conference paper and want to u= se some sections in my thesis. I also like to keep a file with old chapter = drafts for later reference (I could just use git for this, but keeping an o= ld-drafts file around makes some jobs more convenient). One issue that I am= running into is that when I move material with org-refile, footnotes defin= ed in the Footnote section do not move with it.=C2=A0 Additionally, if I tr= y to export a subtree as an org buffer, it does not take footnote definitio= ns with it.

The obvious workaround for both problems is to define footno= tes inline. Another option (the one that I am using currently) is to set or= g-footnote-section to nil, and to set org-footnote-auto-label to 'rando= m. This way footnotes are kept at the bottom of the section, so they move w= ith refile, and they have randomly generated names, so they won't confl= ict with any footnote definitions in the destination file.

This solution works, but I wondered if there was any way to = get org-refile and org-export-org to take footnotes definitions with them, = wherever they are located.
With org-export-org, this seems especially i= mportant as backends are supposed to faithfully export footnotes with their= definitions.

Additionally, is there a way to easily convert numbered foot= notes to randomly named footnotes?

Thanks,
=

=C2=A0Leonard

--001a11c339e6c5b9e504f9e80f39--