From: Vladimir Lomov <email@example.com> To: firstname.lastname@example.org Subject: Re: suggestion to change default org-latex-pdf-process to latexmk Date: Wed, 2 Jun 2021 13:27:48 +0800 [thread overview] Message-ID: <YLcW1L5TQIToet8h@smoon.bkoty.ru> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1728 bytes --] Hello, ** Tim Cross <firstname.lastname@example.org> [2021-06-02 12:56:59 +1000]: > "Bruce D'Arcus" <email@example.com> writes: >> On Tue, Jun 1, 2021 at 9:09 PM Scott Randby <firstname.lastname@example.org> wrote: >> >>> As a constant user of Org's LaTeX export capability, this change would break >>> my ability to export to PDF, and it would be difficult for me to fix. I don't >>> support this change. >> >> Can you explain this, Scott? Why would anything "break'? >> >> And for those that think this is a bad idea, suggested alternatives? >> >> With the status quo; new org-cite users will run latex/pdf output >> process and will be surprised by the results, as there will be no >> citations or bibliography. >> >> I suppose the easy solution is a prominent note in the documentation. >> > I'm guessing Scott is referring to the latexmk not being part of a > 'standard' texlive installation and if not installed, pdf generation > would fail. If you are talking about Linux then there is TeX Live distribution (TUG TeX Live) and texlive packages. latexmk availability depends on how you install TUG TeX Live (full scheme or not, I didn't investigate this I prefer to use full always) but if you are referring to texlive packages (Linux distribution packages) then the latexmk could be available as distribution package. It could be a problem either on Windows (suppose one could use MikTeX but Emacs on Windows is a bit a pain, IMHO) or on Mac but if one uses TUG TeX Live I'm sure there would be latexmk. Of course, it would be best if there will be a note in documentation. [...] --- WBR, Vladimir Lomov -- I can't decide whether to commit suicide or go bowling. -- Florence Henderson [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-06-02 5:28 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 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 [this message] 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=YLcW1L5TQIToet8h@smoon.bkoty.ru \ --email@example.com \ --firstname.lastname@example.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).