From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Beamer export: How to handle overlayarea
Date: Thu, 24 Oct 2013 12:53:52 +0200 [thread overview]
Message-ID: <20131024105352.GL1769@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <CAFniQ7USZ_fiM8bZpckaGx1co_sTOvqbXOscL2DiyXR_rpSyeA@mail.gmail.com>
Hi James,
On Thu, Oct 24, 2013 at 08:43:59AM +0800, James Harkins wrote:
> On Oct 24, 2013 12:58 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> > Headlines also support 'BEAMER_ACT' and 'BEAMER_OPT' properties. The
> > former is translated as an overlay/action specification, or a default
> > overlay specification when enclosed within square brackets. The latter
> > specifies options for the current frame or block, and will automatically
> > be enclosed within square brackets.
>
> That would help.
>
> I'd still like to see something more like a "for-dummies" explanation of
> passing options and arguments to LaTeX entities. I'm not saying the
> documentation is woefully inadequate (hardly that -- Suvayu's page got me
> rather far, and I got stuck on a couple of details). My experience was: it
> never would have occurred to me on my own to use the headline text for
> LaTeX code, and if there was a hint anywhere in the docs to suggest that
> this would be the way to go, I didn't find it. That's a conceptual leap
> that passed me by.
I think I agree with you on this. It is a conceptual leap. I'll add a
TODO item on that Worg page about these kind of tricks.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2013-10-24 10:53 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
2013-10-23 16:59 ` Nicolas Goaziou
2013-10-24 0:43 ` James Harkins
2013-10-24 10:53 ` Suvayu Ali [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=20131024105352.GL1769@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.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).