emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Robert Goldman <rpgoldman@sift.info>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Latex export to documentclass beamer
Date: Mon, 17 Aug 2009 14:19:38 -0400	[thread overview]
Message-ID: <7974.1250533178@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from Robert Goldman <rpgoldman@sift.info> of "Mon, 17 Aug 2009 11:17:09 CDT." <4A898285.9040205@sift.info>

Robert Goldman <rpgoldman@sift.info> wrote:

> Here's another challenge --- is there a good way to handle this in the
> exporter?
> If you use VERBATIM in a beamer frame, then you need to add the optional
> argument "fragile" to the environment, like this:
> \begin{frame}[fragile]
> instead of just
> \begin{frame}
> I'd be surprised if there was a good method for this, but thought I'd ask...

Have you tried adding it unconditionally in the org-export-latex-classes
alist?  I don't think it hurts to have it on by default (it costs a bit
of performance maybe, but it should not be noticeable.) OTOH, verbatim
is a can of worms: it should be avoided if at all possible. It cannot be
used in moving arguments (at all: see


for details.) - and what beamer does with it is a mystery to me - hence
the "avoid at all costs" statement.


  reply	other threads:[~2009-08-17 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 14:43 Latex export to documentclass beamer Robert Goldman
2009-08-17 16:17 ` Robert Goldman
2009-08-17 18:19   ` Nick Dokos [this message]
2009-08-17 18:35     ` Robert Goldman
  -- strict thread matches above, loose matches on Subject: below --
2009-08-09 13:05 RC
2009-08-09 14:17 ` Carsten Dominik
2009-08-09 15:45   ` RC
2009-08-10 11:46     ` Carsten Dominik
2009-08-11  4:14       ` William Henney

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:

  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=7974.1250533178@alphaville.usa.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \


* 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


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