emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org-preview-latex-fragment fails to render in remote files (TRAMP) [8.2.10 (release_8.2.10 @ /usr/local/Cellar/emacs/24.4/share/emacs/24.4/lisp/org/)]
Date: Thu, 05 Mar 2015 18:11:13 -0500	[thread overview]
Message-ID: <87egp3avla.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: m2zj7sn5pu.fsf@Dustins-Macbook-Pro.local.i-did-not-set--mail-host-address--so-tickle-me

Dustin Paluch <dustinpaluch@gmail.com> writes:

> Here's what DOES WORK:
>
> Open a local org file, type in a latex fragment like "\[1 + 2 = 3\]",
> then hit C-c C-x C-l. The fragment is replaced with a png as expected.
>
>
> Here's what DOESN'T WORK:
>
> Open a remote org file via C-x C-f /ssh:user@host:/path/to/file.org RET,
> enter the same latex fragment, and issue the same
> org-preview-latex-fragment command. The fragment will be replaced with a
> blank square. Here is a gif:
>
> http://i.imgur.com/Bb2vgWu.gif
>
> HOWEVER! The image IS created on the remote filesystem in the adjacent
> ltxpng folder as expected.
>
> (First time sending mail from Emacs. I hope this works...)
(it did :-) )
>

That's not a problem with org, it's a problem with images: try executing
the following two calls (with paths appropriate to your environment of
course):

(insert-image
'(image :type png :file "/scp:remote:/tmp/foo.png" :ascent center))

(insert-image
'(image :type png :file "/tmp/foo.png" :ascent center))

and you'll see the same behaviour. Try reporting it as a bug in emacs.

Nick

  reply	other threads:[~2015-03-05 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 15:27 Bug: org-preview-latex-fragment fails to render in remote files (TRAMP) [8.2.10 (release_8.2.10 @ /usr/local/Cellar/emacs/24.4/share/emacs/24.4/lisp/org/)] Dustin Paluch
2015-03-05 23:11 ` Nick Dokos [this message]
2015-03-05 23:14   ` Rasmus
2015-03-07  9:05     ` Nicolas Goaziou

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=87egp3avla.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).