emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BEAMER_act property documented in ox-beamer.el
Date: Wed, 18 Jun 2014 10:52:14 +0200	[thread overview]
Message-ID: <8761jymwg1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ha3i39zo.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 18 Jun 2014 09:19:55 +0100")

Hello,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Tuesday, 17 Jun 2014 at 22:01, Sebastien Vauban wrote:
>
>> I'm trying to understand the sentence from ox-beamer.el:
>>
>>     Headlines also support the "BEAMER_act" property.  [It] is translated as an
>>     overlay/action specification (or a default overlay specification when
>>     enclosed within square brackets).
>>
>> Rewritten, it says that that property is translated as:
>>
>> - a default overlay specification *when enclosed within square brackets*, or
>> - an overlay/action specification *when NOT enclosed within square brackets*.
>>
>> Though, I don't understand exactly what that *default* specification really
>> means. Moreover, I can't get it: without square brackets, PDFLaTeX becomes
>> crazy...
>
> I agree with you: I am not entirely sure what a *default* specification
> means.

See Beamer class user guide about "\begin{frame}" syntax (II.8, p. 59 on
version 3.20). Basically, default specification also applies to all
commands and environments within the frame, as long as they do not
provide their own specification.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2014-06-18  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 20:01 BEAMER_act property documented in ox-beamer.el Sebastien Vauban
2014-06-18  8:19 ` Eric S Fraga
2014-06-18  8:52   ` Nicolas Goaziou [this message]

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=8761jymwg1.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.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).