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

From: Guillaume MULLER <guillaume.muller@emse.fr>
To: emacs-orgmode@gnu.org
Subject: org-beamer improvement?
Date: Fri, 23 Sep 2022 16:49:23 +0200	[thread overview]
Message-ID: <cd5dd45c-303a-fdd9-31c3-ab4a9e854306@emse.fr> (raw)


[-- 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 --]

next             reply	other threads:[~2022-09-23 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 14:49 Guillaume MULLER [this message]
2022-09-24  2:41 ` org-beamer improvement? Ihor Radchenko

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=cd5dd45c-303a-fdd9-31c3-ab4a9e854306@emse.fr \
    --to=guillaume.muller@emse.fr \
    --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).