From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Samuel Schaumburg <eagleeye777@hotmail.de>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Latex Export Difficulties
Date: Thu, 6 Feb 2014 12:29:10 +0000 [thread overview]
Message-ID: <87sirws9ux.fsf@ucl.ac.uk> (raw)
In-Reply-To: <BLU0-SMTP3539D7B999CA0658378762E8B940@phx.gbl> (Samuel Schaumburg's message of "Thu, 6 Feb 2014 10:20:43 +0100")
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Samuel Schaumburg <eagleeye777@hotmail.de> writes:
[...]
> What I learned from my research is that the line has to look like this,
> so that I can compile:
>
> \section{Some Headline \protect\footnote{S. 45}}
>
> This case is quite typicall for me and leads to often manually reworking
> the tex buffer for quite a while, which is not very convenient.
>
> Is there any way I can set up the org latex export to do this
> automatically. Would greatly help my workflow. I am quite a newbie to
> emacs-lisp, so I cannot think of how to do this. Maybe someone can help
> me here
Not an org solution per se but you could redefine \footnote to do what
you want. The example below/attached seems to work. I have no idea if
it breaks the usage of footnote in other places, mind you.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: example redefining footnote in latex --]
[-- Type: text/x-org, Size: 274 bytes --]
* Testing redefinition of footnote
#+latex: \let\origfootnote\footnote
#+latex: \renewcommand{\footnote}{\protect\origfootnote}
** Subheading [fn:1: Which has a very interesting footnote]
This is some really boring text because all the interesting stuff is in the footnote.
[-- Attachment #3: Type: text/plain, Size: 92 bytes --]
HTH,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.2.5h-585-g5f0ca0
next prev parent reply other threads:[~2014-02-06 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:20 Latex Export Difficulties Samuel Schaumburg
2014-02-06 12:29 ` Eric S Fraga [this message]
2014-02-06 12:39 ` Rasmus
2014-02-06 14:33 ` Eric S Fraga
2014-02-06 16:00 ` Florian Beck
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=87sirws9ux.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=eagleeye777@hotmail.de \
--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).