From: "Lennart C. Karssen" <lennart@karssen.org>
To: emacs-orgmode@gnu.org
Subject: Re: Org LaTeX Beamer export and the order of loading packages and theme (XeLaTeX and fonts)
Date: Tue, 9 Jan 2024 22:23:41 +0000 [thread overview]
Message-ID: <e61a7ea9-7fe1-49d2-85b2-94b1011b3715@karssen.org> (raw)
In-Reply-To: <87o7duw3uw.fsf@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1296 bytes --]
Dear Igor,
Thanks for your reply.
On 09-01-2024 22:15, Ihor Radchenko wrote:
> "Lennart C. Karssen" <lennart@karssen.org> writes:
>
>> 1) Is there a way to tell Org to export the #+BEAMER_THEME lines before
>> anything else?
>
> Yes. You can customize "beamer" class in `org-latex-classes' or define a
> custom (for example, "my-beamer") class and add #+LATEX_CLASS: my-beamer
> to the Org file.
Ah, indeed, I hadn't thought of that taking route. I will give it a try.
>
> This will give you full control over the preamble layout.
>
>> 2) Is there a reason why the Beamer theme options are exported after
>> other LaTeX packages? Wouldn't it be better to export the Beamer theme
>> options before loading additional packages? The reason for that being
>> that the theme sets defaults, which can then (potentially) be altered by
>> loading additional packages.
>
> No specific reason that I am aware of.
> Your suggestion sounds reasonable, but I'd like to hear from our LaTeX
> experts first ;)
Of course. Let's see what they have to say.
Lennart.
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
L.C. Karssen
's-Hertogenbosch
The Netherlands
lennart@karssen.org
GPG key ID: A88F554A
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2024-01-09 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 12:02 Org LaTeX Beamer export and the order of loading packages and theme (XeLaTeX and fonts) Lennart C. Karssen
2024-01-09 22:15 ` Ihor Radchenko
2024-01-09 22:23 ` Lennart C. Karssen [this message]
2024-02-12 13:20 ` Ihor Radchenko
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=e61a7ea9-7fe1-49d2-85b2-94b1011b3715@karssen.org \
--to=lennart@karssen.org \
--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).