Hi, That's a tough question ;-) With LaTeX and Beamer we are in a 'ish' situation, because beamer is a latex document class used to create presentations. So, when exporting to beamer, you are using a backed derived from the latex backend. The separation is not as clear as laTeX vs, HTML, which you rightfully mention.
I'm trying to start (stress of trying) to create a cleaner separation in a step-by-step process. Just for this reason, I started by creating the #+BEAMER_CLASS_OPTIONS, which should take precedence over #+LATEX_CLASS_OPTIONS, the final objective being that the beamer exporter just ignores the #+LATEX_CLASS*: keywords, as should the LaTeX exporter ignore the BEAMER_CLASS_OPTIONS. Only then, I'd try to see if we could have the same for #+BEAMER: vs #+LATEX... This may be a lengthy process. And as you say, it should answer many questions from newbies, which we all are in a (thankfully) moving environment like Emacs/org-mode. Best, /PA On Wed, 9 Apr 2025 at 04:34, David Masterson <dsmaster...@icloud.com> wrote: > Pedro Andres Aranda Gutierrez <paag...@gmail.com> writes: > > > On Tue, 8 Apr 2025 at 07:29, David Masterson <dsmaster...@icloud.com> > wrote: > >> > >> Should there be a #+BEAMER_CLASS to go with #+BEAMER_CLASS_OPTIONS > >> ?? > > > > Isn't it enough to it select with > > #STARTUP: beamer > > As I think was asked before, how would you set this up in a single Org > file such that, via (say) org-publish, you could export to: > > + Beamer > + Latex > + HTML > + etc > > In theory, I would like the setup to be "similar" for each to help > newbies (ie. me) not confuse things by asking "why are these > different -- am I missing something?" > > Standards are good. > > -- > David Masterson > -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Sagen's Paradeiser, write BE! Year 1 of the New Koprocracy
