From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: BEAMER_act and special environments
Date: Mon, 11 Nov 2013 09:21:23 +0100 [thread overview]
Message-ID: <20131111082123.GB21748@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <e6599c43-f383-4523-90fa-ca71631aaba4@dewdrop-world.net>
Hi James,
On Mon, Nov 11, 2013 at 11:14:20AM +0800, James Harkins wrote:
>
> I'm not especially familiar with emacs-lisp and I haven't looked at the
> functions for node properties at all. Unfortunately, I'm under a time crunch
> today and I don't have the few hours it would take to get up to speed
> (otherwise, I'd have a go at it myself).
>
> It seems that everything in org-beamer-environments-default supports overlay
> specifications, except beamercolorbox. OK... what about
> org-beamer-environments-special? I found today that B_columns ignores any
> overlay specification given in the heading's properties. That is:
IIUC, columns is a "container" environment for other column
environments. Here is an example from my slides:
\begin{frame}[label=sec-3-4]{Distinguishing CP eigenstates}
\begin{columns}
\begin{column}{0.5\textwidth}
\begin{figure}[htb]
\centering
\includegraphics[width=0.9\textwidth]{fig1.eps}
\caption{m$_\mathrm{ES}$ for B₋ → cc̄K$_S$}
\end{figure}
\end{column}
\begin{column}{0.5\textwidth}
\begin{figure}[htb]
\centering
\includegraphics[width=0.9\textwidth]{fig2.eps}
\caption{ΔE for B₊ → J/ψK$_L$}
\end{figure}
\end{column}
\end{columns}
\end{frame}
So I would think the overlay specification is appropriate for column,
not columns.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2013-11-11 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 3:14 BEAMER_act and special environments James Harkins
2013-11-11 8:11 ` Nicolas Goaziou
2013-11-11 13:24 ` James Harkins
2013-11-11 8:21 ` 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=20131111082123.GB21748@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).