From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Insert #+BEAMER_HEADER_EXTRA before \begin{document}?
Date: Thu, 8 May 2014 16:37:39 +0100 [thread overview]
Message-ID: <87eh04703g.fsf@ucl.ac.uk> (raw)
In-Reply-To: <86a9asie5u.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 8 May 2014 15:38:21 +0200")
On Thursday, 8 May 2014 at 15:38, Sebastien Vauban wrote:
[...]
> The above things are currently (almost, for some) impossible. Changing
> where the #+BEAMER_HEADER placeholder gets inserted makes them possible
> and easy.
but unfortunately would make other things more difficult. For instance,
I often redefine the date command (and sometimes title and author) to do
something different. If the header entries were placed after the use of
theses, things would break for me.
I think the creation of an ...EXTRA directive would be better but I've
argued for this before and have lost that argument.
You can achieve what you want by redefining \title, I would
suggest. Not pretty but it works.
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.6-937-g60502a
next prev parent reply other threads:[~2014-05-08 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 19:01 Insert #+BEAMER_HEADER_EXTRA before \begin{document}? Sebastien Vauban
2014-05-07 22:24 ` Suvayu Ali
2014-05-07 23:26 ` Nick Dokos
2014-05-08 1:38 ` Suvayu Ali
2014-05-08 13:38 ` Sebastien Vauban
2014-05-08 14:49 ` Suvayu Ali
2014-05-08 15:37 ` Eric S Fraga [this message]
2014-05-08 19:55 ` Andreas Leha
[not found] ` <87eh04703g.fsf-hclig2XLE9Zaa/9Udqfwiw@public.gmane.org>
2014-05-21 17:59 ` Sebastien Vauban
2014-06-15 20:10 ` Nicolas Goaziou
[not found] ` <871tuqndck.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2014-06-16 13:42 ` Sebastien Vauban
2014-06-16 14:37 ` Nick Dokos
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=87eh04703g.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=sva-news@mygooglest.com \
/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).