From: Ihor Radchenko <yantar92@gmail.com>
To: Guillaume MULLER <guillaume.muller@emse.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-beamer improvement?
Date: Sat, 24 Sep 2022 10:41:18 +0800 [thread overview]
Message-ID: <87tu4x5wa9.fsf@localhost> (raw)
In-Reply-To: <cd5dd45c-303a-fdd9-31c3-ab4a9e854306@emse.fr>
Guillaume MULLER <guillaume.muller@emse.fr> writes:
> The only thing I miss in org lies in org-beamer: it is the ability to use the star '*' in BEARMER_ACT, with something like:
> * my block1
> :PROPERTIES:
> :BEAMER_ACT: *<1>
> :BEAMER_ENV: block
> :END:
> ...
> I know block do not natively accept *<1> notation, but it would be great if org would detect the * in BEAMER_ACT directive and translate that into some code similar to the one I generate manually (#+LATEX + onslide* + shadow "ignoreheading "closing block).
>
> Any thoughts on this?
What you are proposing is basically to wrap the environment into
\onslide+ \onslide* or \onslide commands.
These commands are only part of the available generic overlay
specifications in Beamer.
What about allowing something like
:BEAMER_ACT: \command<spec>
that will make Beamer wrap the exported environment like
\command<spec>{exported beamer block}?
Also, note that we are currently discussing a more general way to wrap
elements during export in
https://orgmode.org/list/87czbna4e4.fsf@localhost
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
prev parent reply other threads:[~2022-09-24 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:49 org-beamer improvement? Guillaume MULLER
2022-09-24 2:41 ` Ihor Radchenko [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=87tu4x5wa9.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=guillaume.muller@emse.fr \
/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).