From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: Re: Beamer export: How to handle overlayarea Date: Mon, 21 Oct 2013 18:52:41 +0800 Message-ID: References: <87eh7f3pb8.fsf@gmail.com> Reply-To: jamshark70@dewdrop-world.net Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c209765361d604e93e1566 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYD6K-0002lY-9g for emacs-orgmode@gnu.org; Mon, 21 Oct 2013 06:52:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYD6I-00010E-VF for emacs-orgmode@gnu.org; Mon, 21 Oct 2013 06:52:44 -0400 Received: from mail-ob0-x232.google.com ([2607:f8b0:4003:c01::232]:42346) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYD6I-00010A-Ol for emacs-orgmode@gnu.org; Mon, 21 Oct 2013 06:52:42 -0400 Received: by mail-ob0-f178.google.com with SMTP id uz6so5705831obc.9 for ; Mon, 21 Oct 2013 03:52:42 -0700 (PDT) In-Reply-To: <87eh7f3pb8.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: orgmode --001a11c209765361d604e93e1566 Content-Type: text/plain; charset=ISO-8859-1 On Oct 21, 2013 6:12 PM, "Nicolas Goaziou" 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 --001a11c209765361d604e93e1566 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

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:
>
> =A0 *** {0.9\textwidth}{0.7\textheight} =A0 :B_overlayarea:
> =A0 =A0 =A0 :PROPERTIES:
> =A0 =A0 =A0 :BEAMER_env: overlayarea
> =A0 =A0 =A0 :END:

Ah, OK, that's better.

It's not easy to grasp the correct terminology and struc= ture from the available documentation. I do appreciate the excellent help f= rom the list in such cases!

This part of the documentation might benefit from some examp= les of generating different types of beamer syntax -- when to use propertie= s, when to use headline text, etc. I wouldn't have guessed to use the h= eadline 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,&q= uot; 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 enviro= nment definition.
(with an example, but I can't think of one now)

- Additional arguments may be written into the environment&#= 39;s headline, and inserted into the LaTeX string using %r (raw headline te= xt, no processing).
~~

I think it's important to mention it in the section wher= e 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

--001a11c209765361d604e93e1566--