From: Ihor Radchenko <email@example.com>
To: Pride Allman <firstname.lastname@example.org>
Subject: Re: [PATCH] lisp/org-table.el: Use booktabs on org-table-export
Date: Thu, 12 May 2022 17:29:46 +0800 [thread overview]
Message-ID: <87ilqbhzed.fsf@localhost> (raw)
Pride Allman <email@example.com> writes:
> So basically, the export function is doing the overwrite for user options
> but to reduce the number of inconsistency we can't use this patch for only
> one such option.
> Now you explained it I can't think of a way to solve it without rewriting
> the whole thing. Or maybe I need to read the source code more deeply.
> Would it be too much to hope for it to be integrated on the basis that
> things like this can be added for other options in other export backend
> too? Or somehow introduce the global settings there.
As an option, the override arguments can be factored out into
defcustoms. Then, you would have an option to deal with the problem you
Another possibility comes from the fact that the overrides are mostly
copying the defaults or trying to transfer alternative option names into
(list :backend 'latex
:latex-default-table-mode 'table ;; <- this is default
:latex-tables-centered nil <- this is _not_ default. The current default is t
:latex-tables-booktabs (plist-get params :booktabs) <- default is nil
:latex-table-scientific-notation nil <- this is also default
:latex-default-table-environment <- default is "tabular" but :environment is transferred
(or (plist-get params :environment) "tabular"))
Then, we can:
1. Remove options directly overriding the defaults
2. Do not assign :latex-tables-booktabs and
:latex-default-table-environment unless :booktabs and :environment
options are actually provided. Currently, when the latter options are
not set by user (via #+attr_latex), they are treated as if the user
force-set them to nil (because plist-get does not distinguish
(:property nil) and complete absence of :property).
I like the second possibility better because it will make table export
consistent with the rest of export customisation. The downside is that
we can break the existing workflows relying on current behaviour (which
is not too much of a big deal though - we can always document this
change in ORG-NEWS).
The first possibility, on the other hand, will not break the current
behaviour. However, it will only help people who manage to find this new
customisation. We already have too many customisations.
> And considering the answer is no for the previous question; is there a
> workaround for this? Something people use? Because having to manually edit
> the table everytime I export is a bit too much for me.
Yes, there should be a workaround. org-table functions only override
global export settings, not file-local and element-local. That is you
should be able to set #+bind: org-latex-tables-booktabs
org-latex-tables-booktabs. Or #+attr_latex: :booktabs t
Of course, it is not very intuitive and relies on internal knowledge of
prev parent reply other threads:[~2022-05-12 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 22:29 [PATCH] lisp/org-table.el: Use booktabs on org-table-export Pride Allman
2022-05-11 12:19 ` Ihor Radchenko
2022-05-11 17:01 ` Pride Allman
2022-05-12 9:29 ` Ihor Radchenko [this message]
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 \
* 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).