[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Insert #+BEAMER_HEADER_EXTRA before \begin{document}?
From: |
Sebastien Vauban |
Subject: |
Re: [O] Insert #+BEAMER_HEADER_EXTRA before \begin{document}? |
Date: |
Mon, 16 Jun 2014 15:42:16 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (windows-nt) |
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