emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] org.el (org-format-latex-header): put DEFAULT-PACKAGES before PACKAGES
Date: Tue, 14 Jun 2022 14:26:34 +0000	[thread overview]
Message-ID: <7fbcc96f-3b15-5f74-b1ff-2a2f3ed1303d@posteo.eu> (raw)
In-Reply-To: <87sfo7wfce.fsf@localhost>


Ihor Radchenko writes:
> We actually have 2 options here:
> 1. Change the docstring
> 2. Change the template
> Can moving [PACKAGES] up break the existing configs? It might.
> I am inclined to change the docstring instead.

Thanks for having a look at this.

It makes more sense for a package in PACKAGES to depend on a
DEFAULT-PACKAGE than vice versa.

=org-latex-packages-alist= and =org-latex-classes=' are two important
docstrings. People are likely to have crafted their configuration by
reading these documentation.

I've also just checked that by default, for document export,
DEFAULT-PACKAGES are inserted before PACKAGES --- the default
templates from =org-latex-classes= do not include =DEFAULT-PACKAGES=
nor =PACKAGES=, and in this case, =org-splice-latex-header= adds both
default packages and packages at the end, with default packages coming

=org-format-latex-header= is only used to generate images for preview,
and in some cases by ob-latex to compile a document from a LaTeX src


Sébastien Miquel

  reply	other threads:[~2022-06-14 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  9:12 [PATCH] org.el (org-format-latex-header): put DEFAULT-PACKAGES before PACKAGES Sébastien Miquel
2022-06-14 13:21 ` Ihor Radchenko
2022-06-14 14:26   ` Sébastien Miquel [this message]
2022-06-16 12:19     ` Ihor Radchenko
2022-06-17 12:19       ` Sébastien Miquel
2022-06-18  4:50         ` 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:

  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=7fbcc96f-3b15-5f74-b1ff-2a2f3ed1303d@posteo.eu \
    --to=sebastien.miquel@posteo.eu \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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


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