emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: suggestion to change default org-latex-pdf-process to latexmk
Date: Wed, 02 Jun 2021 08:23:54 +0200	[thread overview]
Message-ID: <87o8cohjid.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: 87wnrd8435.fsf@alphaville.usersys.redhat.com

Nick Dokos <ndokos@gmail.com> writes:

> "Bruce D'Arcus" <bdarcus@gmail.com> writes:
>
>> While testing org-cite a few weeks ago, I noticed by default bibtex
>> won't run with natbib export, or biblatex with biblatex export.
>>
>> Since org has not had native citations, this is not surprising.
>>
>> But with org-cite coming soon, this will change.
>>
>> At the time I suggested changing default to use latexmk, which will
>> handle both bibtex and biblatex runs.
>>
>> https://lists.gnu.org/archive/html/emacs-orgmode/2021-05/msg00486.html
>>
>> So what do LaTeX users think about changing the default for
>> "org-latex-pdf-process" to "latexmk"?
>>
>> Is there any reason not to do this?
>>
>
> The only reason I can think of is that it might not be available by
> default, so it will be one more thing for a noob to install before Org mode
> starts "working".

Of course, LaTeX itself, with or without latexmk, is something the noob
will have to install.  So the prerequisite could be "LaTeX with
latexmk".  With regards to Windows, Cygwin has latexmk in the
'texlive-collection-binextra' package and MikTeX has a 'latexmf'
package.  On Debian latexmf is also its own package and thus has to be
installed explicitly.

Personally I use Debian and have "org-latex-pdf-process" set to use
latexmk, so the change in the default wouldn't affect me.

Cheers,

Loris

-- 
This signature is currently under construction.



      reply	other threads:[~2021-06-02  6:24 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
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 [this message]

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=87o8cohjid.fsf@hornfels.zedat.fu-berlin.de \
    --to=loris.bennett@fu-berlin.de \
    --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).