From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: BEAMER_act property documented in ox-beamer.el Date: Wed, 18 Jun 2014 10:52:14 +0200 Message-ID: <8761jymwg1.fsf@nicolasgoaziou.fr> References: <864mzj8fw0.fsf@somewhere.org> <87ha3i39zo.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50977) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxBaq-0005L2-N4 for emacs-orgmode@gnu.org; Wed, 18 Jun 2014 04:51:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxBaj-0004JO-7t for emacs-orgmode@gnu.org; Wed, 18 Jun 2014 04:51:44 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:36697) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxBaj-0004Ir-14 for emacs-orgmode@gnu.org; Wed, 18 Jun 2014 04:51:37 -0400 In-Reply-To: <87ha3i39zo.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 18 Jun 2014 09:19:55 +0100") 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: Sebastien Vauban Cc: emacs-orgmode@gnu.org Hello, Eric S Fraga 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