emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: James Harkins <jamshark70@gmail.com>
To: orgmode <emacs-orgmode@gnu.org>
Subject: BEAMER_act and special environments
Date: Mon, 11 Nov 2013 11:14:20 +0800	[thread overview]
Message-ID: <e6599c43-f383-4523-90fa-ca71631aaba4@dewdrop-world.net> (raw)

Hi,

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:

**** Header							  :B_columns:
     :PROPERTIES:
     :BEAMER_env: columns
     :BEAMER_act: 2-
     :END:
(... with some BMCOL headings underneath...)

-->

\begin{columns}
.. blah blah...
\end{columns}

.. where I would have hoped for "\begin{columns}<2->"

I was able to work around the limitation by wrapping the "columns" 
environments within "onlyenv" environments. But it seems to me that it 
might be nicer to be able to write the overlay directly into the affected 
environment.

I don't mind poking around the code, but I'd need some tips. I can see 
where B_columns gets formatted, but I'm not clear how to check for a 
BEAMER_act property.

Thanks,
hjh

next             reply	other threads:[~2013-11-11  3:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11  3:14 James Harkins [this message]
2013-11-11  8:11 ` BEAMER_act and special environments Nicolas Goaziou
2013-11-11 13:24   ` James Harkins
2013-11-11  8:21 ` 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=e6599c43-f383-4523-90fa-ca71631aaba4@dewdrop-world.net \
    --to=jamshark70@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

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).