From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: The orgframe construct in the Beamer exporter as a default needs a rethink
Date: Fri, 1 Mar 2024 17:17:46 +0100 [thread overview]
Message-ID: <E6C88BC9-80C1-4B93-A6F2-BAE6899DFACC@gmail.com> (raw)
In-Reply-To: <87h6hqj5we.fsf@ucl.ac.uk>
HI Eric,
Neither did I, until I had to do my slide decks ;-)
Anyhow, since this feature solves issues, we could think about another approach.
A quick and dirty fix would be to check whether org-beamer-frame-environment is “frame”
and if so, not redefine the environment.
The second step in this discussion is whether we want org-beamer-frame-environment
To be “orgbeamer” or “beamer" by default. The first meaning most of us would need to customize it
or redefine it in a local variable. The second would mean that whenever there are ‘weird’ slides
you set the value to “orgframe” or whatever, and that would be it. With a big CAVEAT: you
Will not be able to do the <beamer>/<handout> trick on them.
Best, /PA
> El 1 mar 2024, a las 17:03, Fraga, Eric <e.fraga@ucl.ac.uk> escribió:
>
> On Friday, 1 Mar 2024 at 12:33, Pedro Andres Aranda Gutierrez wrote:
>> I needed to go back to stock org-mode (as included in Emacs) because
>> the ‘orgframe’ as defined right now kills my slide decks.
>> I have been using the construct
>>
>> ** Title
>> :PROPERTIES:
>> :BEAMER_act: <beamer>
>> :END:
>
> I do similar and hadn't realised that there had been any breaking
> changes as, I guess, I haven't had to create a new slides since the
> orgframe change came through. This is a rather serious breaking change
> and would affect hundreds of slides for me (two modules I teach not to
> mention research talks).
>
>> I don’t know how often the orgframe is needed (I haven’t needed it in
>> the last years of making my presentations with org-mode), but wouldn’t
>> it be more sensible to write
>>
>> ** Title
>> :PROPERTIES:
>> :BEAMER_env: orgframe
>> :END:
>
> This sounds reasonable (to me). I didn't follow the orgframe discussion
> closely so cannot say whether this would achieve what motivated the
> changes.
>
> --
> : Eric S Fraga, with org release_9.6.19-1215-g67d937 in Emacs 30.0.50
next prev parent reply other threads:[~2024-03-01 16:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 11:33 The orgframe construct in the Beamer exporter as a default needs a rethink Pedro Andres Aranda Gutierrez
2024-03-01 16:03 ` Fraga, Eric
2024-03-01 16:17 ` Pedro Andres Aranda Gutierrez [this message]
2024-03-01 17:23 ` Pedro Andres Aranda Gutierrez
2024-03-01 23:11 ` [BUG] " Leo Butler
2024-03-02 6:24 ` Pedro Andres Aranda Gutierrez
2024-03-02 6:39 ` Pedro Andres Aranda Gutierrez
2024-03-02 8:25 ` Pedro Andres Aranda Gutierrez
2024-03-02 12:22 ` Ihor Radchenko
2024-03-02 19:03 ` Pedro Andres Aranda Gutierrez
2024-03-04 11:10 ` Ihor Radchenko
2024-03-09 8:33 ` Pedro Andres Aranda Gutierrez
2024-03-12 12:33 ` Ihor Radchenko
2024-03-12 20:32 ` Leo Butler
2024-03-13 7:16 ` Pedro Andres Aranda Gutierrez
2024-03-13 13:12 ` Ihor Radchenko
2024-03-14 15:49 ` Leo Butler
2024-03-15 14:02 ` Ihor Radchenko
2024-03-16 13:12 ` Leo Butler
2024-03-16 23:24 ` Leo Butler
2024-03-17 9:53 ` Ihor Radchenko
2024-03-17 13:18 ` Leo Butler
2024-03-17 14:36 ` Ihor Radchenko
2024-03-02 12:21 ` Ihor Radchenko
2024-03-02 12:20 ` 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=E6C88BC9-80C1-4B93-A6F2-BAE6899DFACC@gmail.com \
--to=paaguti@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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
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).