emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] A proposal to add LaTeX attributes to verse blocks
Date: Tue, 04 May 2021 09:22:51 +1000	[thread overview]
Message-ID: <87im3ze50y.fsf@gmail.com> (raw)
In-Reply-To: <87im419xu3.fsf@gmail.com>

Timothy <tecosaur@gmail.com> writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>> Is the verse package loaded automatically already?  I did not see any
>> change in the patch to that aspect and when I export a simple test, the
>> package is not loaded.
> Wouldn't it be nice if there was something in-between loading the
> kitchen sink and manually adding packages*... [ foreshadowing ;) ]

Will be interesting to see what you are 'foreshadowing'.

Personally, I find the current options pretty flexible with
'org-latex-classes and support for the macro like placeholders
[PACKAGES, DEFAULT_PACKAGES, EXTRA and their negators] and the ability
to add packages with LATEX_HEADER and LATEX_HEADER_EXTRA file options.
I'm often quite surprised how little people seem to take advantage of
'org-latex-classes and the LATEX_CLASS; file option to define custom
document formats. You can easily define an 'empty' class which only
includes packages you add with LATEX_HEADER: or LATEX_HEADER_EXTRA for

It is with 'tweaking' Latex packages I've seen people get into trouble.
There can often be some unexpected results when you fail to load or load
packages in a different order. Testing is notoriously difficult as you
also need a lot of different test input data to get good coverage and
adequately test the impact changes to loaded Latex packages causes.
Without detailed knowledge of the latex based exporters, it isn't always
obvious how/where specific Latex packages are used. It would be
important to ensure any mechanism designed to make it easier to
customize what packages are loaded that we don't also end up generating
more bug rports about broken export formatting. 

Tim Cross

  reply	other threads:[~2021-05-04  0:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 17:23 [PATCH] A proposal to add LaTeX attributes to verse blocks Juan Manuel Macías
2021-01-03 10:25 ` TEC
2021-01-03 13:07   ` Juan Manuel Macías
2021-01-03 13:08     ` TEC
2021-01-07 18:52       ` Juan Manuel Macías
2021-05-01 10:58         ` Bastien
2021-05-01 11:46           ` Juan Manuel Macías
2021-05-02 10:24           ` Eric S Fraga
     [not found]           ` <87tunlxws3.fsf@ucl.ac.uk>
2021-05-02 11:09             ` Juan Manuel Macías
2021-05-02 11:31             ` Timothy
2021-05-03 23:22               ` Tim Cross [this message]
2021-05-08  7:31           ` Juan Manuel Macías
2021-05-15 13:46             ` Bastien
2021-05-01 10:58         ` Timothy
  -- strict thread matches above, loose matches on Subject: below --
2020-12-17 17:11 [patch] " Juan Manuel Macías
2021-01-03 10:22 ` TEC

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=87im3ze50y.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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