From: Bastien <firstname.lastname@example.org>
To: Matt Huszagh <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: [PATCH] babel latex headers and image generation commands
Date: Sat, 24 Oct 2020 14:30:36 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
sorry for the delayed answer.
Matt Huszagh <email@example.com> writes:
> Bastien <firstname.lastname@example.org> writes:
>> * lisp/ob-latex.el (org-babel-latex-preamble): New option for LaTeX
>> preamble customization.
>> "New option" is quite standard, an "option" being a customizable
>> variable. In this case, "New option" would probably be enough, given
>> the name of the option is quite self-explanatory. Also, some find it
>> pedantic, but "LaTeX" is the correct spelling in a changelog I guess.
> Fixed in new patch (attached).
Applied as ae35a3459, thanks!
>> The first line of the docstring should contain a sentence, so you'd
>> need to have a new paragraph after "runtime to the LaTeX preamble."
> Also fixed. Making the first line a full sentence means that some lines
> are a little longer than 80 characters. Is this acceptable?
>> What for users who don't have inkscape?
> This is just a default, but I could use a dvisvgm command as the default
> instead? Either way, converting a PDF to SVG will require an executable
> outside Emacs, but I guess dvisvgm is more likely to be installed for
> people using a texlive installation. My personal preference for inkscape
> is because it should handle all PDF inputs, whereas there are some cases
> where dvisvgm may fail (see
> https://github.com/mgieseki/dvisvgm/issues/139) due to changes in
> ghostscript. Still, dvisvgm generally does a very good job with PDF
> inputs. Let me know your thoughts, I'd be happy to set the default to a
> dvisvgm command instead.
Let's see what people think when they try it after 9.5.
Can you provide a patch against etc/ORG-NEWS announce this?
next prev parent reply other threads:[~2020-10-24 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 7:39 babel latex headers and image generation commands Matt Huszagh
2020-02-04 21:19 ` Matt Huszagh
2020-02-04 23:38 ` Matt Huszagh
2020-02-10 7:21 ` Bastien
[not found] ` <email@example.com>
2020-08-29 7:02 ` Matt Huszagh
2020-09-02 17:32 ` [PATCH] " Matt Huszagh
2020-09-02 18:53 ` Matt Huszagh
2020-09-06 6:18 ` Bastien
2020-09-09 19:43 ` Matt Huszagh
2020-10-24 12:30 ` Bastien [this message]
2020-10-24 16:39 ` Matt Huszagh
2020-12-14 8:19 ` Bastien
2020-09-06 5:59 ` Bastien
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).