From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-beamer :BEAMER_ACT: ignored on columns
Date: Thu, 13 Oct 2022 08:59:01 +0000 [thread overview]
Message-ID: <87tu483z8d.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87wn94tpjx.fsf@localhost> (Ihor Radchenko's message of "Thu, 13 Oct 2022 10:39:30 +0800")
On Thursday, 13 Oct 2022 at 10:39, Ihor Radchenko wrote:
> Take your time. What I do not want here is introducing new bugs. I am
> not familiar with ox-beamer and do not want to miss anything subtle.
Thank you. I'll update you in due course.
> Or <...>. In particular,
> (org-beamer--normalize-argument raw-actions 'action)
> , will return <raw-actions> (possibly stripping duplicate <>)
> Looking at 12.7 Splitting a Frame into Multiple Columns section of the
> beamer manual, it should be safe to use <raw-actions>.
That is likely true. I have never put actions on columns before in
beamer, only on items or more low level constructs, so I will need to
play around a little to ensure we don't break anything. With [<...>],
things work so far (for columns), however.
--
: Eric S Fraga, with org release_9.5.5-840-g52be6f in Emacs 29.0.50
next prev parent reply other threads:[~2022-10-13 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41d13343-d278-2474-ba8f-88d24621ab30@housseini.me>
2022-10-05 6:38 ` [BUG] org-beamer :BEAMER_ACT: ignored on columns reza
2022-10-05 8:19 ` Fraga, Eric
2022-10-06 3:06 ` Ihor Radchenko
2022-10-06 8:01 ` Fraga, Eric
2022-10-07 13:16 ` Fraga, Eric
2022-10-08 6:10 ` Ihor Radchenko
2022-10-10 7:38 ` Fraga, Eric
2022-10-12 6:00 ` Ihor Radchenko
2022-10-12 7:42 ` Fraga, Eric
2022-10-13 2:39 ` Ihor Radchenko
2022-10-13 8:59 ` Fraga, Eric [this message]
2022-11-14 5:48 ` Ihor Radchenko
2024-01-31 14:29 ` 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=87tu483z8d.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).