From: Max Nikulin <manikulin@gmail.com>
To: Timothy <orgmode@tec.tecosaur.net>,
Karthik Chikmagalur <karthikchikmagalur@gmail.com>
Cc: mherstine@pobox.com, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Run latex more than once for LaTeX src block evaluation
Date: Tue, 26 Mar 2024 19:13:35 +0700 [thread overview]
Message-ID: <2fc939a6-3211-4627-b4e9-274d7b6179c0@gmail.com> (raw)
In-Reply-To: <87msqof1kh.fsf@localhost>
On 24/03/2024 15:58, Ihor Radchenko wrote:
> Max Nikulin writes:
>> On 22/03/2024 05:55, Michael wrote:
>>> I have a small patch for `org-preview-latex-process-alist' making
>>> the default setting for LaTeX source block evaluation be running
>>> latex three times (instead of the current one).
>>
>> I suspect it may make the LaTeX preview feature unacceptably slow for
>> documents heavily loaded with math snippets.
>
> Then, we may instead use latexmk - it will run latex as many times as
> necessary.
Sorry I have no experience with latexmk. At least a fallback should be
available if this script is not installed.
The LaTeX preview feature is close to dangerous per se. With latexmk the
barrier may be even lower. Some users may have -shell-escape enabled in
latexmk configuration. I hope, it is not possible to force latexmk
execute something weird by spitting a crafted message into logs.
I have no idea how to enable preview for trusted files only without
ruining usability.
next prev parent reply other threads:[~2024-03-26 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 22:55 [PATCH] Run latex more than once for LaTeX src block evaluation Michael
2024-03-22 12:56 ` Ihor Radchenko
2024-03-22 17:23 ` Michael
2024-03-23 14:42 ` Ihor Radchenko
2024-04-05 6:41 ` Karthik Chikmagalur
2024-03-24 8:04 ` Max Nikulin
2024-03-24 8:58 ` Ihor Radchenko
2024-03-26 12:13 ` Max Nikulin [this message]
2024-03-27 19:34 ` Michael
2024-03-28 12:17 ` Ihor Radchenko
2024-04-05 0:00 ` Michael
2024-04-29 9:24 ` Ihor Radchenko
2024-04-05 0:04 ` Michael
2024-05-05 10:44 ` Ihor Radchenko
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=2fc939a6-3211-4627-b4e9-274d7b6179c0@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=karthikchikmagalur@gmail.com \
--cc=mherstine@pobox.com \
--cc=orgmode@tec.tecosaur.net \
/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).