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.fr...@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
