From: Stefan Nobis <stefan-ml@snobis.de>
To: emacs-orgmode@gnu.org
Subject: Re: suggestion to change default org-latex-pdf-process to latexmk
Date: Wed, 02 Jun 2021 18:07:51 +0200 [thread overview]
Message-ID: <m1sg2045d4.fsf@nobis-it.eu> (raw)
In-Reply-To: <cb85b222-2de3-9ad2-bd1e-3fc9391cef4f@gmail.com> (Scott Randby's message of "Wed, 2 Jun 2021 11:39:44 -0400")
Scott Randby <srandby@gmail.com> writes:
> (1) Which one of the above suggestions should I use? I don't want
> interactions when I'm exporting. I don't want to have to mess with a
> configuration file either.
> (2) How many shell commands will org-latex-pdf-process need? Right
> now there are three. Replace those three with just one latexmk?
I have
--8<---------------cut here---------------start------------->8---
(setq org-latex-pdf-process '("latexmk -f -pdf -%latex -outdir=%o %f"))
--8<---------------cut here---------------end--------------->8---
in my Emacs configuration. The nice thing with latexmk is, that a
single call will suffice. It reads the generated log and checks
whether multiple calls to the LaTeX engine are necessary (after each
run it check whether another run is need, up-to the configurable
maximum of 5 runs). Therefore in some cases (depending on used LaTeX
packages and commands) latexmk may even produce the PDF faster, if
only one or two passes are necessary. But sometimes LaTeX thinks it
may need more passes (e.g. having undefined references, unstable
output due to dynamically generated things at page breaks for example
with cleveref and varioref where floats/references are put on one page
in one run and another page in the following run) - and in these cases
creating the PDF may take a bit longer due to the maximum of 5
(instead of only 3) runs.
Hope that helps a little bit.
--
Until the next mail...,
Stefan.
next prev parent reply other threads:[~2021-06-02 16:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 15:36 Bruce D'Arcus
2021-06-01 15:52 ` Juan Manuel Macías
2021-06-01 16:36 ` Timothy
2021-06-01 16:45 ` Bruce D'Arcus
2021-06-01 17:03 ` Timothy
2021-06-01 17:41 ` Bruce D'Arcus
2021-06-02 5:33 ` Stefan Nobis
2021-06-02 15:39 ` Scott Randby
2021-06-02 16:07 ` Stefan Nobis [this message]
2021-06-02 16:29 ` Colin Baxter
2021-06-02 16:41 ` Robert Pluim
2021-06-02 16:47 ` Bruce D'Arcus
2021-06-02 18:40 ` Greg Minshall
2021-06-02 23:28 ` Tim Cross
2021-06-02 17:00 ` Stefan Nobis
2021-06-03 5:35 ` Colin Baxter
2021-06-02 17:36 ` Scott Randby
2021-06-02 0:00 ` Tim Cross
2021-06-02 1:09 ` Scott Randby
2021-06-02 1:25 ` Bruce D'Arcus
2021-06-02 2:56 ` Tim Cross
2021-06-02 5:27 ` Vladimir Lomov
2021-06-02 6:07 ` Stefan Nobis
2021-06-02 8:26 ` Tim Cross
2021-06-02 12:07 ` Bruce D'Arcus
2021-06-02 14:26 ` Colin Baxter
2021-06-02 22:35 ` Tim Cross
2021-06-02 15:43 ` Scott Randby
2021-06-02 16:22 ` Dr. Arne Babenhauserheide
2021-06-02 22:53 ` Tim Cross
2021-06-02 22:44 ` Tim Cross
2021-06-04 11:28 ` Dr. Arne Babenhauserheide
2021-06-02 8:40 ` Juan Manuel Macías
2021-06-02 1:09 ` Nick Dokos
2021-06-02 6:23 ` Loris Bennett
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=m1sg2045d4.fsf@nobis-it.eu \
--to=stefan-ml@snobis.de \
--cc=emacs-orgmode@gnu.org \
--subject='Re: suggestion to change default org-latex-pdf-process to latexmk' \
/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
Code repositories for project(s) associated with this 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).