From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: BEAMER_act property documented in ox-beamer.el
Date: Tue, 17 Jun 2014 22:01:19 +0200 [thread overview]
Message-ID: <864mzj8fw0.fsf@somewhere.org> (raw)
Hello,
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...
--8<---------------cut here---------------start------------->8---
* Overlay/action specification enclosed within square brackets
The following 2 cases are exported in exactly the same LaTeX code.
** With angular brackets
:PROPERTIES:
:BEAMER_act: [<+->]
:END:
- Item 1
- Item 2
** Without angular brackets
:PROPERTIES:
:BEAMER_act: [+-]
:END:
- Item 1
- Item 2
* Overlay/action specification NOT enclosed within square brackets :noexport:
The follow 2 cases make PDFLaTeX infloop...
** Without angular brackets
:PROPERTIES:
:BEAMER_act: <+->
:END:
- Item 1
- Item 2
** Without angular brackets
:PROPERTIES:
:BEAMER_act: +-
:END:
- Item 1
- Item 2
--8<---------------cut here---------------end--------------->8---
Anyone undestanding more than I am?
Best regards,
Seb
--
Sebastien Vauban
next reply other threads:[~2014-06-17 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 20:01 Sebastien Vauban [this message]
2014-06-18 8:19 ` BEAMER_act property documented in ox-beamer.el Eric S Fraga
2014-06-18 8:52 ` Nicolas Goaziou
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=864mzj8fw0.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 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).