emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Eric S Fraga <esflists@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX (not Beamer) export options
Date: Fri, 15 Dec 2017 12:12:17 +0000	[thread overview]
Message-ID: <87r2rw42ce.fsf@gmail.com> (raw)
In-Reply-To: <m2ind9s0i4.fsf@gmail.com> (Ken Mankoff's message of "Thu, 14 Dec 2017 18:05:55 +0100")

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

On Thursday, 14 Dec 2017 at 18:05, Ken Mankoff wrote:
> Hi Org List,
>
> Is there an easy way to specify #+LATEX_HEADER options that will not
> be used when exporting to Beamer? I can do the opposite
> -#+BEAMER_HEADER lines are not exported to LaTeX. But I have some
> LaTeX config options that are getting in the way when exporting to
> Beamer.

Hopefully somebody else will answer with a proper org solution but, in
the absence of anything else, you could wrap the LaTeX code in the
latex_header with an \if looking for something that is unique to beamer
and only include the code if not beamer.  Something along the lines of

#+latex_header: \ifx\frametitle\undefined\usepackage{somepackage}\fi

which seems to work.  \usepackage{somepackage} is what you actually want
when not using beamer.  Replace with your own stuff.  You can make it
more readable by doing:

# only for LaTeX and not beamer
#+latex_header: \ifx\frametitle\undefined
#+latex_header: \usepackage{somepackage}
#+latex_header: \usepackage{another}
#+latex_header: \fi


HTH,
eric

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.4-214-ge8b71b

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

next prev parent reply	other threads:[~2017-12-15 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 17:05 LaTeX (not Beamer) export options Ken Mankoff
2017-12-15 12:12 ` Eric S Fraga [this message]
2017-12-18 15:56   ` Ken Mankoff

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=87r2rw42ce.fsf@gmail.com \
    --to=esflists@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \
    /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

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