From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Beamer export: How to handle overlayarea
Date: Mon, 21 Oct 2013 18:52:41 +0800 [thread overview]
Message-ID: <CAFniQ7Wj9foX4Tos_dXEaqRQuAK+4NdfebabsNBT3Hck+0rC9g@mail.gmail.com> (raw)
In-Reply-To: <87eh7f3pb8.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
On Oct 21, 2013 6:12 PM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> Optional arguments are in square brackets in LaTeX. Try %r instead, so
> you can write:
>
> *** {0.9\textwidth}{0.7\textheight} :B_overlayarea:
> :PROPERTIES:
> :BEAMER_env: overlayarea
> :END:
Ah, OK, that's better.
It's not easy to grasp the correct terminology and structure from the
available documentation. I do appreciate the excellent help from the list
in such cases!
This part of the documentation might benefit from some examples of
generating different types of beamer syntax -- when to use properties, when
to use headline text, etc. I wouldn't have guessed to use the headline text
because I was thinking of parameters or arguments.
> > Also, side note, [1] seems not to document BEAMER_OPT for environments
> > within a frame. Reading this page, you would think you could only use
> > it for frames. I had to dig into the source code to find how to
> > populate %o.
>
> Would you mind suggesting a better phrasing?
Under "Block environments and overlay specifications," where it discusses
custom environments, I would add:
~~
- Environment options may be given using the BEAMER_opt property. They will
be enclosed in square brackets and inserted where %o appears in the
environment definition.
(with an example, but I can't think of one now)
- Additional arguments may be written into the environment's headline, and
inserted into the LaTeX string using %r (raw headline text, no processing).
~~
I think it's important to mention it in the section where it can be used.
My faulty conclusion was based on the fact that the only mention of _opt is
in a section about frames.
hjh
hjh
[-- Attachment #2: Type: text/html, Size: 2095 bytes --]
next prev parent reply other threads:[~2013-10-21 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 7:52 Beamer export: How to handle overlayarea James Harkins
2013-10-21 8:49 ` Sebastien Vauban
2013-10-21 10:02 ` Suvayu Ali
2013-10-21 10:12 ` Nicolas Goaziou
2013-10-21 10:52 ` James Harkins [this message]
2013-10-23 16:59 ` Nicolas Goaziou
2013-10-24 0:43 ` James Harkins
2013-10-24 10:53 ` Suvayu Ali
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=CAFniQ7Wj9foX4Tos_dXEaqRQuAK+4NdfebabsNBT3Hck+0rC9g@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=n.goaziou@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
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).