From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jack Kamm Subject: Displaying remote images Date: Thu, 28 Nov 2019 09:09:56 -0800 Message-ID: <8736e8sza3.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:53112) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iaNJS-00065r-F3 for emacs-orgmode@gnu.org; Thu, 28 Nov 2019 12:10:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iaNJJ-0002fa-5K for emacs-orgmode@gnu.org; Thu, 28 Nov 2019 12:10:35 -0500 Received: from mail-pj1-x1034.google.com ([2607:f8b0:4864:20::1034]:33307) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iaNJI-0002Ew-Sx for emacs-orgmode@gnu.org; Thu, 28 Nov 2019 12:10:33 -0500 Received: by mail-pj1-x1034.google.com with SMTP id r67so4368252pjb.0 for ; Thu, 28 Nov 2019 09:10:29 -0800 (PST) Received: from localhost (199-83-220-90.PUBLIC.monkeybrains.net. [199.83.220.90]) by smtp.gmail.com with ESMTPSA id y62sm1701378pfg.45.2019.11.28.09.10.24 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Nov 2019 09:10:24 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org When trying to display a remote image file in an org-mode buffer, I only see a blank square instead of the image. This is a longstanding problem, and there was an attempt to patch it in 2014, but the patch was never accepted: https://lists.gnu.org/archive/html/emacs-orgmode/2014-11/msg00583.html The fault might be with image.el rather than with org-mode itself -- for example, when I execute the following elisp, I get the same blank box: (insert-image (create-image "/scp:pi:/home/pi/foo.png")) However, if I open the remote file in its own buffer using image-mode, I can correctly view the image. Anyways, I would like to try and fix this, but not sure whether we should pursue a fix in org.el (as in the linked patch), or in image.el, or elsewhere. Any advice on how to proceed here?