emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Lennart C. Karssen" <lennart@karssen.org>
Cc: "Emacs orgmode" <emacs-orgmode@gnu.org>,
	"Daniel Fleischer" <danflscr@gmail.com>,
	"Leo Butler" <Leo.Butler@umanitoba.ca>,
	"Juan Manuel Macías" <maciaschain@posteo.net>
Subject: Re: Org LaTeX Beamer export and the order of loading packages and theme (XeLaTeX and fonts)
Date: Tue, 09 Jan 2024 22:15:19 +0000	[thread overview]
Message-ID: <87o7duw3uw.fsf@localhost> (raw)
In-Reply-To: <0aba4e92-b878-4a37-b0e2-0848dcbef5a2@karssen.org>

"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.

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 ;)

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-01-09 22:13 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 [this message]
2024-01-09 22:23   ` Lennart C. Karssen
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=87o7duw3uw.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=Leo.Butler@umanitoba.ca \
    --cc=danflscr@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lennart@karssen.org \
    --cc=maciaschain@posteo.net \
    /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).