emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scott Randby <srandby@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: suggestion to change default org-latex-pdf-process to latexmk
Date: Wed, 2 Jun 2021 11:39:44 -0400	[thread overview]
Message-ID: <cb85b222-2de3-9ad2-bd1e-3fc9391cef4f@gmail.com> (raw)
In-Reply-To: <m1tumg6dbe.fsf@nobis-it.eu>

On 6/2/21 1:33 AM, Stefan Nobis wrote:
> "Bruce D'Arcus" <bdarcus@gmail.com> writes:
> 
>> Here's the current command for the "latexmk" option:
> 
>> "latexmk -g -pdf -pdflatex=\"%latex\" -outdir=%o %f"
> 
>> ... and here's what you have, minus shell-escape.
> 
>> "latexmk -f -pdf -%latex -interaction=nonstopmode -output-directory=%o %f"
> 
> The option "-interaction=nonstopmode" forbids user interaction (like
> asking for a missing file). Without this explicit option latexmk uses
> "-interaction=batchmode" by default - in this case some diagnotic
> messages to the terminal (not log file) are suppressed. Thus the
> default option from latexmk might suffice.
> 
> Regarding "-f" versus "-g" I personally would slightly prefer "-f" for
> performance reasons. With "-g" the document will always be newly
> generated, even if nothing changed. This is only useful if the latexmk
> config (or some environment variable) has changed. Other changes
> should be detectable by latexmk, so "-f" should suffice.
> 
> The options "-output-directory" and "-outdir" are synonyms.
> 
> Regarding the choise of engine: "-pdflatex=\"%latex\"" explicitly sets
> the command (including options) to be called by latexmk, without
> letting latexmk know that the engine changed. Using "-%latex" (e.g.
> the option "-lualatex" or "-xelatex") lets latexmk know that a
> different engine should be used.
> 
> This matters at least for xelatex, because latexmk can utilize some
> optimizations if it knows that xetex is used. In this case the first
> runs only produce .xdv files and only the last run will produce the
> full pdf to save time (see also option "-pdfxe" which is triggered by
> "-xelatex").
> 
> Therefore I would tend to use this call:
> 
>      "latexmk -f -pdf -%latex -outdir=%o %f"
> 
> All other aspects of latexmk should be configured via config file
> (IMHO).
> 
>> In any case, whatever the command is, clearly it should.
> 

I'm no longer sure that a change would break my ability to export to PDF. I'm using Linux with TeX Live, and latexmk is available. I'm willing to try changing org-latex-pdf-process to one of the above suggestions, but I have some questions. I've never used latexmk, and I really depend on Org to set things up so that they just work out of the box. It took me a long time to figure out how to get Emacs to find TeX so that previewing LaTeX fragments works (the solution is not in the Org manual).

(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?

Scott Randby



  reply	other threads:[~2021-06-02 15:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 15:36 suggestion to change default org-latex-pdf-process to latexmk 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 [this message]
2021-06-02 16:07             ` Stefan Nobis
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=cb85b222-2de3-9ad2-bd1e-3fc9391cef4f@gmail.com \
    --to=srandby@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).