From: Ihor Radchenko <yantar92@posteo.net>
To: Emmanuel Charpentier <emm.charpentier@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] LaTeX preview should use a subdirectory in /tmp
Date: Wed, 17 Apr 2024 20:18:44 +0000 [thread overview]
Message-ID: <87zftr4uaj.fsf@localhost> (raw)
In-Reply-To: <59096bd365ccf1cb3ec2b45b0f2ecb5c508ded34.camel@free.fr>
Emmanuel Charpentier <emm.charpentier@free.fr> writes:
>> Assuming that your `org-preview-latex-default-process' is using the
>> default value of 'dvipng, does it help if you change the image
>> convertor
>> command to use absolute path?
>
> I didn't know that one could do that : the placeholders are not well
> documented...
Yeah. This particular option is missing from the docstring of
`org-preview-latex-process-alist'.
>> (plist-put (alist-get 'dvipng org-preview-latex-process-alist)
>> :image-converter
>> '("dvipng -D %D -T tight -o %O %F"))
>
> Nope, same problem : the *Org Preview LaTeX Output* buffer says :
>
> ../../../../../tmp/orgtexSyy18r.dvi: No such file or directory
> This is dvipng 1.15 Copyright 2002-2015 Jan-Ake Larsson
>
> If I understand it correctly, the %F placeholder should be an
> *absolute* filename. It is not...
>
> Couldn't the output directory of the :latex-compiler element being
> hardcoded to, say, the curerent directory or a subdirectory thereof,
> and ditto for the input directory of :image-converter ?
What if you do M-x trace-function <RET> org-compile-file-commands <RET>
and run the preview.
Then, a buffer should appear listing the command expansions used during
the preview process. May you then share that buffer?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-04-17 20:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 15:21 [BUG] LaTeX preview should use a subdirectory in /tmp Emmanuel Charpentier
2024-04-17 16:48 ` Ihor Radchenko
2024-04-17 20:04 ` Emmanuel Charpentier
2024-04-17 20:18 ` Ihor Radchenko [this message]
2024-04-17 20:41 ` Emmanuel Charpentier
2024-04-18 12:23 ` Emmanuel Charpentier
2024-04-19 11:56 ` Ihor Radchenko
2024-04-19 15:00 ` emm.charpentier
2024-04-20 12:49 ` Max Nikulin
2024-05-02 10:30 ` Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2024-04-17 15:12 copropriete27ruemoret
2024-03-25 10:40 Max Nikulin
2024-03-25 11:40 ` Ihor Radchenko
2024-03-25 12:49 ` Max Nikulin
2024-03-26 11:29 ` Max Nikulin
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=87zftr4uaj.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=emm.charpentier@free.fr \
/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).