From: "briangpowell ." <briangpowellms@gmail.com>
To: Jack Kamm <jackkamm@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Displaying remote images
Date: Fri, 29 Nov 2019 00:36:10 -0500 [thread overview]
Message-ID: <CAFm0skE_Uez5HbOzJUm2aWrOoTbF=R3yc=Mt_ekKC81_pREKAQ@mail.gmail.com> (raw)
In-Reply-To: <87tv6nsaqh.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
* Great, see a lot of interest and use of image-mode.el, suggest you check
out this thread
https://emacs.stackexchange.com/questions/3432/display-images-in-eshell-with-iimage-mode
** Suggest you check out and use iimage-mode.el --it may help ...that's
iimage-mode.el rather than, or in addition to, your use of image-mode.el
On Thu, Nov 28, 2019 at 9:20 PM Jack Kamm <jackkamm@gmail.com> wrote:
> I've attached a patch which implements displaying remote images.
>
> > 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
>
> Compared to the previous attempt from 2014, I think my patch is simpler
> -- it doesn't require creating any temp files.
>
> > 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:
>
> After doing some reading, I learned that image.el doesn't really create
> the image. Instead, create-image simply creates a blank string with a
> text property pointing to the image file location, and the rendering of
> the image gets handled later by the C code (for example, png_load_body()
> in image.c), which doesn't know how to read remote image files.
>
> Since I wasn't comfortable trying to get the C code to read the remote
> file, I instead took the approach used by image-mode.el, which reads the
> remote image file and passes its contents directly to create-image,
> instead of just passing the filename.
>
>
[-- Attachment #2: Type: text/html, Size: 2308 bytes --]
next prev parent reply other threads:[~2019-11-29 5:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 17:09 Displaying remote images Jack Kamm
2019-11-28 21:50 ` briangpowell .
2019-11-29 1:39 ` Jack Kamm
2019-11-29 2:00 ` Jack Kamm
2019-11-29 5:36 ` briangpowell . [this message]
2019-12-02 20:27 ` Nick Dokos
2019-12-02 22:39 ` briangpowell .
2019-12-07 14:41 ` Jack Kamm
2020-01-19 22:17 ` Jack Kamm
2020-01-21 16:39 ` Nicolas Goaziou
2020-01-22 15:31 ` stardiviner
2020-01-25 0:28 ` Jack Kamm
2020-02-01 10:51 ` 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='CAFm0skE_Uez5HbOzJUm2aWrOoTbF=R3yc=Mt_ekKC81_pREKAQ@mail.gmail.com' \
--to=briangpowellms@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@gmail.com \
/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).