From: Ihor Radchenko <yantar92@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [DISCUSSION]: LaTeX - include the xcolor package in the packages list
Date: Sun, 15 Sep 2024 08:17:23 +0000 [thread overview]
Message-ID: <87ed5l72lo.fsf@localhost> (raw)
In-Reply-To: <113128B8-EC80-4C8C-89C1-0E2384CE7958@gmail.com>
Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>> I guess that you are referring to
>>
>> When using listings, you also need to make use of LaTeX package
>> "listings". The "color" LaTeX package is also needed if you
>> would like color too. These can simply be added to
>> org-latex-packages-alist, using customize or something like:
>>
>> (require 'ox-latex)
>> (add-to-list 'org-latex-packages-alist '("" "listings"))
>> (add-to-list 'org-latex-packages-alist '("" "color"))
>
> A first step would be to use xcolor here. It gives just much more control over colors, if and when you need it.
I do not see any downside changing our recommendation from using color
to using xcolor in the docstrings.
>> We can indeed include color package, but I do not see why we should do
>> it by default. We may instead include it conditionally, only when
>> listings backend is selected by the user.
>> Just as it is done for engraved.
>
> I would say that we include graphicx by default, even when we are not going to use it in many documents. In my case it is a 50/50 of using graphics vs- pure text documents ;-)
My stance is to minimize the number of loaded packages to the bare
minimum. If something is not strictly necessary, we do not load it.
Loading a bunch of extra LaTeX packages increases export time.
In the future, when we have the new LaTeX preview branch [1] merged, we
will cut the number of loaded LaTeX packages even more, only loading the
packages that are necessary to export the specific document
contents. For example, if the exported Org file does not contain images,
no image-related packages will be used during Latex export.
[1] https://list.orgmode.org/87lek2up0w.fsf@tec.tecosaur.net/
--
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>
prev parent reply other threads:[~2024-09-15 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 6:07 [DISCUSSION]: LaTeX - include the xcolor package in the packages list Pedro Andres Aranda Gutierrez
2024-09-08 17:37 ` Ihor Radchenko
2024-09-09 5:20 ` Pedro Andres Aranda Gutierrez
2024-09-09 6:05 ` Ihor Radchenko
2024-09-09 7:27 ` Pedro Andres Aranda Gutierrez
2024-09-09 7:49 ` Ihor Radchenko
2024-09-11 5:28 ` Pedro Andres Aranda Gutierrez
2024-09-15 8:17 ` Ihor Radchenko [this message]
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=87ed5l72lo.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).