emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Just thinking...
Date: Sat, 9 Mar 2024 09:31:12 +0100	[thread overview]
Message-ID: <CAO48Bk_ZOawdpCKoinknUyqT7Bev1rXaeHrQSA5Lb_hZyLK4RQ@mail.gmail.com> (raw)
In-Reply-To: <87bk7qxh6c.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

You are right. It is easy to do from emacs-lisp scripts, looking for
LATEX_CLASS in a document and then deciding to use the org-latex-... or the
org-beamer-... functions, but it looks much more difficult in org.el itself
:(
It's just that it would look much more elegant to have only one. For me
Beamer is just a LaTeX 'feature'...

/PA

On Thu, 7 Mar 2024 at 15:10, Ihor Radchenko <yantar92@posteo.net> wrote:

> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
> > duplicating export entries for LaTeX and Beamer makes the interface not
> > exactly clean.
> > We do have the LaTeX class, which should be "beamer" (I hope) for Beamer
> > presentations, right?
> >
> > So why not use that to decide internally between (org-latex-export-...)
> and
> > (org-beamer-...) and then have a unified interaction with the user?
>
> I am afraid that implementing this would be a kludge. For technical
> reasons.
>
> For example, Org export parses keywords depending on the selected export
> backend. Selected in advance.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>


-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 2497 bytes --]

  reply	other threads:[~2024-03-09  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  9:46 Just thinking Pedro Andres Aranda Gutierrez
2024-03-07 14:14 ` Ihor Radchenko
2024-03-09  8:31   ` Pedro Andres Aranda Gutierrez [this message]
2024-03-12 19:03     ` 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=CAO48Bk_ZOawdpCKoinknUyqT7Bev1rXaeHrQSA5Lb_hZyLK4RQ@mail.gmail.com \
    --to=paaguti@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).