From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org,
Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
Subject: Re: Insert #+BEAMER_HEADER_EXTRA before \begin{document}?
Date: Mon, 16 Jun 2014 15:42:16 +0200 [thread overview]
Message-ID: <867g4hhsxz.fsf@somewhere.org> (raw)
In-Reply-To: <871tuqndck.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> (Nicolas Goaziou's message of "Sun, 15 Jun 2014 22:10:19 +0200")
Hello Nicolas,
> Sebastien Vauban writes:
>
>> But the whole point is that is DOES NOT even WORK for a couple of
>> things, such as modifying base colors of a theme:
>>
>> #+BEAMER_HEADER: \setbeamercolor{frametitle}{bg=blue}
>>
>> won't work because of the misplacement of the BEAMER_HEADER placeholder
>> regarding to the (color) theme: the above line will be placed before the
>> choice of the theme... TOO EARLY.
>>
>> On the contrary, adding it in the above title command (already in the
>> LaTeX document, that is) is TOO LATE.
Thanks for answering to this.
> I do not see how to solve this without either adding a new keyword or
> extending `org-latex-classes' to support another location (e.g.
> "[BEAMER-THEME]"). Actually, both may be needed.
IIUC the code of ox-beamer:
--8<---------------cut here---------------start------------->8---
;; 1. Time-stamp.
(and (plist-get info :time-stamp-file)
(format-time-string "%% Created %Y-%m-%d %a %H:%M\n"))
;; 2. Document class and packages.
...
(concat (org-element-normalize-string
(plist-get info :latex-header))
(org-element-normalize-string
(plist-get info :latex-header-extra))
(plist-get info :beamer-header-extra)))))
info)))
;; 3. Insert themes.
--8<---------------cut here---------------end--------------->8---
all 3 following keywords:
- #+LATEX_HEADER:
- #+LATEX_HEADER_EXTRA:
- #+BEAMER_HEADER:
are going to the exact same place, right?
Then, why not saying that, for example, both #+LATEX_HEADER
and #+LATEX_HEADER_EXTRA go to the current place, and
drop #+BEAMER_HEADER at the end of the preamble?
Maybe I see: because you want to associate such a place to an official
"location" such as [BEAMER-THEME], so that it can be enabled or
disabled?
> About the keyword, my only concern is that #+LATEX_HEADER_EXTRA has
> already a specific meaning, which is different from the one we're going
> to implement.
Can you restate once what the difference is between #+LATEX_HEADER
and #+LATEX_HEADER_EXTRA? It never has been clear to me, yet...
Thanks.
> So, #+BEAMER_HEADER_EXTRA might be confusing. OTOH
> I cannot think of anything much better.
>
> WDYT?
Maybe something more semantic, then, such
as #+BEAMER_HEADER_PREAMBLE_END or #+BEAMER_HEADER_END_PREAMBLE?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-06-16 13:42 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
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 [this message]
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=867g4hhsxz.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org \
--cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg-wOFGN7rlS/M9smdsby/KFg@public.gmane.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).