emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Adding functionality to org-latex-classes
Date: Sun, 31 Dec 2023 14:40:32 +0000	[thread overview]
Message-ID: <87ttny77vj.fsf@localhost> (raw)
In-Reply-To: <CAO48Bk-ZbhgoOiKVkK6zECwA9aDFvSAWn5qq6NbMVUs7opOUAw@mail.gmail.com>

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> I was just wondering whether it would be possible to add further
> functionality to org-latex-classes and would like to start a discussion ;-)
>
> My use case is the following:
>
> The document class is tightly coupled with  ~org-latex-subtitle-format~
> and  ~org-latex-subtitle-separate~. Koma-script classes, for example, need
> those variables to be defined with file or directory local variables in
> order to take full profit of the layouts. If we found a way of
> accommodating them in the class definitions, the fuzz of the extra
> variables could easily be overcome.

We may extend `org-latex-classes' to allow custom backend option values.
For example,

  (latex-subtitle-format . value)
  (latex-subtitle-separate . value)

Then, we can use these values as the overrides when the variables are
not set explicitly as buffer-locals or as in-buffer/subtree export
keywords.

-- 
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>


  reply	other threads:[~2023-12-31 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 16:57 Adding functionality to org-latex-classes Pedro Andres Aranda Gutierrez
2023-12-31 14:40 ` Ihor Radchenko [this message]
2023-12-31 17:00   ` Pedro Andres Aranda Gutierrez

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=87ttny77vj.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=paaguti@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).