From: Michael <sp1ff@runbox.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Max Nikulin <manikulin@gmail.com>,
Timothy <orgmode@tec.tecosaur.net>,
Karthik Chikmagalur <karthikchikmagalur@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: [PATCH] Run latex more than once for LaTeX src block evaluation
Date: Thu, 04 Apr 2024 17:00:38 -0700 [thread overview]
Message-ID: <861q7kwub6.fsf@runbox.com> (raw)
In-Reply-To: <87cyretut7.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Michael <sp1ff@runbox.com> writes:
>
>> Should we perhaps have different variables for preview & Org
>> source block evaluation?
>
> Likely yes.
>
> In fact, ob-latex is making use of
> `org-preview-latex-process-alist'
> only in a single cond branch in `org-babel-execute:latex' - when
> we have
> :file foo.png
>
> However, that branch assumes that
> `org-preview-latex-default-process' is
> 'dvipng (the default value). If one changes it to, say dvisvgm,
> the
> generated image will not be a .png image:
>
> (setq org-preview-latex-default-process 'dvisvgm)
>
> #+begin_src latex :results file link :file test.png
> x^2
> #+end_src
>
> #+RESULTS:
> [[attachment:test.png]]
>
> ^ This is actually an svg image, renamed to "test.png".
>
> So, it makes sense for `org-babel-execute:latex' to override
> `org-preview-latex-default-process' temporarily, to something
> actually
> generating .png file.
Sorry-- got sidetracked by something else. I see what you
mean. OK, so the proposal is: change the ".png" branch in
`org-babel-execute:latex' to override `org-preview-process-alist'
with something that will:
- actually produce a PNG formatted file
- by default, run latex more than once, tho this could of
- course be customized
--
Michael <mherstine@pobox.com>
next prev parent reply other threads:[~2024-04-05 0:03 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
2024-03-27 19:34 ` Michael
2024-03-28 12:17 ` Ihor Radchenko
2024-04-05 0:00 ` Michael [this message]
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=861q7kwub6.fsf@runbox.com \
--to=sp1ff@runbox.com \
--cc=emacs-orgmode@gnu.org \
--cc=karthikchikmagalur@gmail.com \
--cc=manikulin@gmail.com \
--cc=mherstine@pobox.com \
--cc=orgmode@tec.tecosaur.net \
--cc=yantar92@posteo.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).