emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug report: org-preview-latex fails when using tramp
Date: Thu, 06 Oct 2022 17:00:21 +0800	[thread overview]
Message-ID: <87mta94996.fsf@localhost> (raw)
In-Reply-To: <87sfuaqxk5.fsf@gmail.com>

Timothy <tecosaur@gmail.com> writes:

> Confirmed.
> I just tried this by creating an Org file on a Debian server (I run OpenSUSE
> with TexLive 2021). From looking at the `*Org Preview LaTeX Output*' buffer, it
> appears that the temp file is created on my local machine, and then the process
> is called on the remote machine.
> ┌────
> │ This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=latex)
> │  restricted \write18 enabled.
> │ entering extended mode
> │ ! I can't find file `/tmp/orgtexToEnS4.tex'.
> └────
> Having a look at `org-create-formula-image', I suspect this is due to the
> `make-temp-name' call at
> <https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/lisp/org.el#n16521>.
> Perhaps `tramp-make-tramp-temp-name' could be useful?

But will it be efficient? We will need to transfer images between the
remote host and the Emacs host.

Should we instead arrange the LaTeX call to be done on user side all the

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>

      reply	other threads:[~2022-10-06  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30  5:44 Bug report: org-preview-latex fails when using tramp Dov Grobgeld
2021-12-30  8:50 ` Timothy
2022-10-06  9:00   ` Ihor Radchenko [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:

  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=87mta94996.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \


* 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


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).