From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [beamer] frame arguments must be in envargs, not extra
Date: Fri, 08 Jan 2010 09:29:49 +0000 [thread overview]
Message-ID: <87ljg9ndv6.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <35D64293-EAC0-4FBF-8E8F-BE20F0C6ABB7@gmail.com>
At Thu, 7 Jan 2010 10:38:00 +0100,
Carsten Dominik wrote:
> On Jan 7, 2010, at 1:10 AM, Eric S Fraga wrote:
> > the documentation for beamer support,
> >
> > http://orgmode.org/worg/org-tutorials/org-beamer.php
> >
> > under the "Special properties" heading suggests that the BEAMER_extra
> > property can be used to specify options for the environment.
> > For
> > frames, trying for instance "[shrink=30]", this doesn't work.
>
> No, this is not what BEAMER_extra is for, this is the function
> BEAMER_envargs. BEAMER_extra is just plain LaTeX that will be inserted.
Ah, okay. That makes sense and BEAMER_envargs does indeed work. Thanks!
> I don't this the document says differently, can you point out exactly
> where you got this from?
I guess it was me reading too much into what you say about the extra
property. The problem is that it mentions frames so I thought it
could be used to modify frame behaviour. However, anything placed in
BEAMER_extra doesn't actually end up right after the \begin{frame} but
instead is placed after the \frametitle directive. I have no problem
with this but it is slightly inconsistent with the wording for
BEAMER_extra in that the extra text does not get placed immediately
after the environment start.
Thanks again,
eric
next prev parent reply other threads:[~2010-01-08 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 0:10 [beamer] frame arguments must be in envargs, not extra Eric S Fraga
2010-01-07 9:38 ` Carsten Dominik
2010-01-08 9:29 ` Eric S Fraga [this message]
2010-01-08 15:31 ` Carsten Dominik
2010-01-08 19:29 ` Eric S Fraga
2010-01-08 19:55 ` Carsten Dominik
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=87ljg9ndv6.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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 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.