From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: image-size
Date: Thu, 20 Jun 2013 22:57:10 +0200 [thread overview]
Message-ID: <m3zjukv6u1.fsf@stories.gnus.org> (raw)
In-Reply-To: <83k3loo66g.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Jun 2013 23:53:11 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> I can't see anything in the imagemagick code that talks to X, so I think
>> it's a general Emacs image thingie.
>
> IT CANNOT BE TRUE!!!! IF IT WERE TRUE, I COULD NOT HAVE USED IMAGES
> ON WINDOWS, where there's no X.
Of course there is no X stuff on Windows. But if you're running over X,
lookup_image pushes data over X, for some reason or other. I have no
idea what the reason might be, but perhaps somebody else does.
>> Anyway, this has led me to consider this a bit more. Sure, this is
>> faster than 46 seconds:
>>
>> (benchmark-elapse (image-size (create-image
>> "/home/larsi/Catalogue/html/scans/BAD0013/BAD0013-1-l.jpg") t))
>> => 0.226372938
>>
>> But on the other hand, the next time we open the file to scale it down,
>> we'll have to decode the image yet again, which will take 0.23 seconds
>> once again.
>
> If it is in the cache, Emacs will fetch it from there.
It would decode twice with the two-part `image-size'/`put-image' code,
since `image-size' would then not put things into the cache.
As Chong said:
> You have to replace the call to lookup_image in `image-size' with a
> new function that avoids loading the image.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2013-06-20 20:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 10:04 image-size Lars Magne Ingebrigtsen
2013-06-20 12:18 ` image-size Lars Magne Ingebrigtsen
2013-06-20 16:52 ` image-size Eli Zaretskii
2013-06-20 16:01 ` image-size Eli Zaretskii
2013-06-20 16:50 ` image-size Lars Magne Ingebrigtsen
2013-06-20 16:55 ` image-size Lars Magne Ingebrigtsen
2013-06-20 17:16 ` image-size Eli Zaretskii
2013-06-20 17:54 ` image-size Lars Magne Ingebrigtsen
2013-06-20 18:15 ` image-size Eli Zaretskii
2013-06-20 18:31 ` image-size Eli Zaretskii
2013-06-20 18:46 ` image-size Lars Magne Ingebrigtsen
2013-06-20 19:11 ` image-size Eli Zaretskii
2013-06-20 19:18 ` image-size Lars Magne Ingebrigtsen
2013-06-20 19:37 ` image-size Eli Zaretskii
2013-06-20 19:52 ` image-size David Engster
2013-06-20 20:50 ` image-size Eli Zaretskii
2013-06-20 19:34 ` image-size Lars Magne Ingebrigtsen
2013-06-20 19:42 ` image-size Eli Zaretskii
2013-06-20 19:52 ` image-size Lars Magne Ingebrigtsen
2013-06-20 20:53 ` image-size Eli Zaretskii
2013-06-20 20:57 ` Lars Magne Ingebrigtsen [this message]
2013-06-20 21:06 ` image-size Lars Magne Ingebrigtsen
2013-06-21 6:12 ` image-size Eli Zaretskii
2013-06-20 21:42 ` image-size Jan Djärv
2013-06-21 0:46 ` image-size YAMAMOTO Mitsuharu
2013-06-21 6:27 ` image-size Lars Magne Ingebrigtsen
2013-06-26 8:25 ` image-size YAMAMOTO Mitsuharu
2013-06-26 10:39 ` image-size YAMAMOTO Mitsuharu
2013-06-26 12:04 ` image-size Lars Magne Ingebrigtsen
2013-06-27 0:46 ` image-size Lars Magne Ingebrigtsen
2013-06-27 2:49 ` image-size Stefan Monnier
2013-06-28 2:46 ` image-size YAMAMOTO Mitsuharu
2013-06-28 3:12 ` image-size Juanma Barranquero
2013-06-28 3:45 ` image-size YAMAMOTO Mitsuharu
2013-06-21 6:15 ` image-size Eli Zaretskii
2013-06-21 7:34 ` image-size Jan Djärv
2013-06-21 8:27 ` image-size Eli Zaretskii
2013-06-21 9:03 ` image-size Jan Djärv
2013-06-21 9:07 ` image-size Lars Magne Ingebrigtsen
2013-06-21 9:58 ` image-size Eli Zaretskii
2013-06-21 9:57 ` image-size Eli Zaretskii
2013-06-21 6:13 ` image-size Eli Zaretskii
2013-06-21 15:54 ` image-size Willem Rein Oudshoorn
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zjukv6u1.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.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).