emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <tecosaur@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug report: org-preview-latex fails when using tramp
Date: Thu, 30 Dec 2021 16:50:11 +0800	[thread overview]
Message-ID: <87sfuaqxk5.fsf@gmail.com> (raw)
In-Reply-To: <CA++fsGFaFmct9MYOeABfnD4Tnrh8GzxG+RCPSk44PYq=egSXbg@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]


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
Perhaps `tramp-make-tramp-temp-name' could be useful?

All the best,

[-- Attachment #1.2: Type: text/html, Size: 8348 bytes --]

  reply	other threads:[~2021-12-30  8:59 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 [this message]
2022-10-06  9:00   ` 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:

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


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