From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: BEAMER_HEADER in `org-latex-classes'
Date: Thu, 07 Nov 2013 18:51:10 +0100 [thread overview]
Message-ID: <8638n8hzht.fsf@somewhere.org> (raw)
Hello,
In the `org-latex-classes' documentation (and in the Org Beamer documentation),
I don't see how to include or exclude lines passed through the #+BEAMER_HEADER
keyword.
╭────
│ The header string
│ -----------------
│
│ The HEADER-STRING is the header that will be inserted into the
│ LaTeX file. It should contain the \documentclass macro, and
│ anything else that is needed for this setup. To this header, the
│ following commands will be added:
│
│ - Calls to \usepackage for all packages mentioned in the
│ variables `org-latex-default-packages-alist' and
│ `org-latex-packages-alist'. Thus, your header definitions
│ should avoid to also request these packages.
│
│ - Lines specified via "#+LATEX_HEADER:" and
│ "#+LATEX_HEADER_EXTRA:" keywords.
│
│ If you need more control about the sequence in which the header
│ is built up, or if you want to exclude one of these building
│ blocks for a particular class, you can use the following
│ macro-like placeholders.
│
│ [DEFAULT-PACKAGES] \usepackage statements for default packages
│ [NO-DEFAULT-PACKAGES] do not include any of the default packages
│ [PACKAGES] \usepackage statements for packages
│ [NO-PACKAGES] do not include the packages
│ [EXTRA] the stuff from #+LATEX_HEADER(_EXTRA)
│ [NO-EXTRA] do not include #+LATEX_HEADER(_EXTRA) stuff
╰────
Is there a solution for those lines?
Best regards,
Seb
--
Sebastien Vauban
next reply other threads:[~2013-11-07 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 17:51 Sebastien Vauban [this message]
2013-11-07 20:22 ` BEAMER_HEADER in `org-latex-classes' Nicolas Goaziou
2013-11-08 9:40 ` Sebastien Vauban
2013-11-08 10:05 ` Nicolas Goaziou
2013-11-08 10:27 ` Sebastien Vauban
2013-11-08 10:57 ` Nicolas Goaziou
2013-11-08 11:19 ` Sebastien Vauban
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8638n8hzht.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.