From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>, Emacs-orgmode@gnu.org
Subject: Re: Beamer export: How to handle overlayarea
Date: Thu, 24 Oct 2013 08:43:59 +0800 [thread overview]
Message-ID: <CAFniQ7USZ_fiM8bZpckaGx1co_sTOvqbXOscL2DiyXR_rpSyeA@mail.gmail.com> (raw)
In-Reply-To: <87bo2fudnn.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]
On Oct 24, 2013 12:58 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> There are two things to consider: what belongs to the manual, and what
> belongs to `org-beamer-environments-extra' docstring.
>
> I think it is reasonable for the manual not to talk about %o, %r... but,
> instead, simply point to the variable name.
OK.
> 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.
FWIW, I often raise a similar point among SuperCollider devs, noting that
we generally do a decent job of documenting class interfaces, but not such
a great job of explaining to people who don't eat, breathe and sleep SC how
to put the pieces together. That leads to questions such as [1] on the
mailing list. Really basic use case, but this competent user is confused...
meaning, the collective docs aren't doing a thorough job.
This sort of doc would be appropriate for worg, but probably not the
manual. If I have time while traveling, I'll draft up a few paragraphs --
but I don't know all the implementation details so I'd certainly need
another pair of eyes.
hjh
[1] http://article.gmane.org/gmane.comp.audio.supercollider.user/102850
[-- Attachment #2: Type: text/html, Size: 2397 bytes --]
next prev parent reply other threads:[~2013-10-24 0:44 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 [this message]
2013-10-24 10:53 ` Suvayu Ali
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=CAFniQ7USZ_fiM8bZpckaGx1co_sTOvqbXOscL2DiyXR_rpSyeA@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=n.goaziou@gmail.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).