* org-beamer improvement?
@ 2022-09-23 14:49 Guillaume MULLER
2022-09-24 2:41 ` Ihor Radchenko
0 siblings, 1 reply; 2+ messages in thread
From: Guillaume MULLER @ 2022-09-23 14:49 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1.1.1: Type: text/plain, Size: 1166 bytes --]
Hi again,
While writing my previous email, I just thought of another thing. As it is unrelated to the other one, I'm creating a second email...
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:
+ my content1
* my block2
:PROPERTIES:
:BEAMER_ACT: *<2>
:BEAMER_ENV: block
:END:
+ my content2
which would make the 2nd block appear "in place" of the 1rst one.
I end up doing things like:
#+LATEX: \onlide*<1>{
* my block1
* @@l:@@
:PROPERTIES:
:BEAMER_ENV: ignoreheading
:END:
+ my content1
#+LATEX: }
#+LATEX: \onlide*<2>{
* my block2
* @@l:@@
:PROPERTIES:
:BEAMER_ENV: ignoreheading
:END:
+ my content2
#+LATEX: }
Its works but it makes my org files look very ugly :{
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?
--
Guillaume MULLER
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 673 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: org-beamer improvement?
2022-09-23 14:49 org-beamer improvement? Guillaume MULLER
@ 2022-09-24 2:41 ` Ihor Radchenko
0 siblings, 0 replies; 2+ messages in thread
From: Ihor Radchenko @ 2022-09-24 2:41 UTC (permalink / raw)
To: Guillaume MULLER; +Cc: emacs-orgmode
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-09-24 2:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-23 14:49 org-beamer improvement? Guillaume MULLER
2022-09-24 2:41 ` Ihor Radchenko
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).