From: Antoine Levitt <antoine.levitt@gmail.com>
To: ding@gnus.org
Subject: Re: Asynchroneous image retrieval in HTML rendering
Date: Thu, 28 Apr 2011 22:03:47 +0200 [thread overview]
Message-ID: <87r58mi1ng.fsf@gmail.com> (raw)
In-Reply-To: <87bozwfw84.fsf@gmail.com>
24/04/11 00:18, Antoine Levitt
> Right now, with mm-text-html-renderer set to 'shr or 'gnus-w3m, loading
> images on slow servers takes ages, and hangs emacs (for instance, check
> out gwene.com.wordpress.terrytao, which has latex code rendered into
> lots of small images). 'w3m (with emacs-w3m installed) results in a nice
> smooth display, and does not hang emacs.
>
> Is there a setting I missed somewhere? If not, how feasible is it to add
> asynchroneous image retrieval to shr? Sorry if the subject has already
> come up, but I didn't find anything about it.
Alright, so this doesn't seem to generate a lot of enthusiasm. If it's
too hard to implement full asynchroneous retrieval, is it possible to
block images declared as being of size 1x1, which are heavily used as
trackers in RSS feeds (for instance, gwene.uk.co.guardian)? It's a
cheap hack, unlikely to break anything, and it'd save some nasty freezes
on slow connections (the combination of prefetching, lots of images and
slow DNS lookup is particularly annoying, causing long uninterruptible
freezes)
next prev parent reply other threads:[~2011-04-28 20:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 22:18 Antoine Levitt
2011-04-28 20:03 ` Antoine Levitt [this message]
2011-04-29 9:04 ` Julien Danjou
2011-04-29 9:18 ` Antoine Levitt
2011-04-29 10:01 ` Julien Danjou
2011-04-29 20:34 ` Antoine Levitt
2011-05-01 15:13 ` Lars Magne Ingebrigtsen
2011-05-01 15:23 ` Antoine Levitt
2011-05-01 15:42 ` Lars Magne Ingebrigtsen
2011-05-01 16:06 ` Lars Magne Ingebrigtsen
2011-05-01 16:34 ` Adam Sjøgren
2011-05-01 16:45 ` Lars Magne Ingebrigtsen
2011-05-01 17:15 ` Antoine Levitt
2011-05-02 7:52 ` Antoine Levitt
2011-05-02 14:30 ` Lars Magne Ingebrigtsen
2011-05-02 14:53 ` Antoine Levitt
2011-05-02 15:17 ` Lars Magne Ingebrigtsen
2011-05-02 17:08 ` Lars Magne Ingebrigtsen
2011-05-02 17:24 ` Antoine Levitt
2011-05-02 17:40 ` Lars Magne Ingebrigtsen
2011-05-02 21:52 ` Antoine Levitt
2011-05-04 18:40 ` Simon Josefsson
2011-05-30 20:55 ` Lars Magne Ingebrigtsen
2011-05-05 8:25 ` Julien Danjou
2011-05-30 20:56 ` Lars Magne Ingebrigtsen
2011-05-05 10:48 ` Ted Zlatanov
2011-05-05 10:58 ` Julien Danjou
2011-05-05 11:17 ` Antoine Levitt
2011-05-05 13:51 ` Ted Zlatanov
2011-05-05 14:01 ` David Engster
2011-05-05 14:07 ` Julien Danjou
2011-05-05 15:05 ` Lars Magne Ingebrigtsen
2011-05-05 19:49 ` David Engster
2011-05-05 20:07 ` Lars Magne Ingebrigtsen
2011-05-05 14:25 ` David Engster
2011-05-05 14:34 ` Antoine Levitt
2011-05-05 14:59 ` David Engster
2011-05-05 15:00 ` David Engster
2011-05-02 17:53 ` Lars Magne Ingebrigtsen
2011-05-02 18:18 ` Lars Magne Ingebrigtsen
2011-05-02 17:12 ` Ted Zlatanov
2011-05-02 17:20 ` Lars Magne Ingebrigtsen
2011-05-02 21:18 ` Steinar Bang
2011-05-02 22:40 ` Lars Magne Ingebrigtsen
2011-05-03 14:09 ` Ted Zlatanov
2011-05-03 18:48 ` Steinar Bang
2011-05-02 21:15 ` Steinar Bang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r58mi1ng.fsf@gmail.com \
--to=antoine.levitt@gmail.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).