emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: suggestion to change default org-latex-pdf-process to latexmk
Date: Wed, 02 Jun 2021 18:26:03 +1000	[thread overview]
Message-ID: <87y2bs6589.fsf@gmail.com> (raw)
In-Reply-To: <m1pmx46bq1.fsf@nobis-it.eu>


Stefan Nobis <stefan-ml@snobis.de> writes:

> Tim Cross <theophilusx@gmail.com> writes:
>
>> One reason is that latexmk is not installed on some systems.
>
> Just after starting to write that this is false nowadays I realized
> you are right. :)
>
> See: https://mg.readthedocs.io/latexmk.html
>
> For macOS latexmk is distributed with the default TeX installation
> MacTeX for quite some years (IIRC at least since 2012). And it is
> working OOTB.
>
> As far as I know the default TeX installation for Windows is MikTeX
> (is this still true?), which also includes latexmk but lacks the Perl
> part (therefore Perl needs to be installed manually). But there is
> TeXLive for Windows and as far as I understand in this case Perl is
> also installed and latexmk works OOTB.
>
> A manual installation of TeXLive for Linux should also install latexmk
> (and Perl should also be available on next to every Linux box). Only
> some distributions bundle latexmk in a separate package - that should
> be easy to install (but breaks PDF creation if forgotten).
>
> Therefore: latexmk is available on all plattforms and in most cases it
> is already installed with the TeX system or easily installable. But
> not in all cases does it work OOTB and requires more work like
> installing Perl on Windows.
>
> In my opinion its worth to depend on this tool as it makes handling
> LaTeX documents much easier. On the other hand it may raise the bar
> for some users just to high. Hard to say.
>
> An alternative may be to use latexmk only if citations are found (new
> feature, new dependencies). Or a wrapper that checks whether latexmk
> is available and works (e.g. trying to call "latexmk --version") and
> falls back to the old routine of manually running the engine and
> bibtex/biber if necessary.

The more I think about it, I think the best solution would be to update
the code which sets the default and have it check for latexmk. If it is
found, set it as the default and if it is not found, set the existing
default. This would have minimum impact on users and allow those who
have installed latexmk to get the benefits while not forcing those who
don't need it to install it.


-- 
Tim Cross


  reply	other threads:[~2021-06-02  8:28 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
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 [this message]
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=87y2bs6589.fsf@gmail.com \
    --to=theophilusx@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).