Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Async pre-treatment of articles
Date: Sat, 28 Aug 2010 22:27:00 +0200	[thread overview]
Message-ID: <m3wrrasctn.fsf@quimbies.gnus.org> (raw)

Reading articles with pictures external pictures in them (for instance,
the Gwene groups) is somewhat awkward.  You first get the text, and then
a few second later, the pictures are filled in, and the text moves
around.  It's annoying.

I thought at first that the problem was that Emacs displayed the
pictures slowly, but the problem is probably just that it takes a while
for w3m to fetch the images.  Re-reading articles where w3m has cached
the images is very fast.

So my immediate idea would be to add some sort of async pre-rendering of
messages.  That is, from the nntp pre-fetch code (or somewhere), point
w3m at the message.  However, for that to happen, Gnus really has to do
all the decoding and charset stuff and Content-Transfer-Encoding stuff,
so that's a pretty big chunk of code to run from an async hook...

However, it occurs to me just now that if we special-case for CTE: 8bit,
then I could just point w3m at a throwaway buffer containing the next
article(s), and let it do its stuff there...

Would that be to special-casey for general usefulness? 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




             reply	other threads:[~2010-08-28 20:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 20:27 Lars Magne Ingebrigtsen [this message]
2010-08-28 20:34 ` Adam Sjøgren
2010-08-28 20:39   ` Adam Sjøgren
2010-08-28 20:44     ` Lars Magne Ingebrigtsen
2010-08-28 20:55       ` Adam Sjøgren
2010-08-28 20:59         ` Adam Sjøgren
2010-08-28 21:18           ` Lars Magne Ingebrigtsen
2010-08-28 21:21             ` Adam Sjøgren
2010-08-28 21:28               ` Lars Magne Ingebrigtsen
2010-08-28 21:44                 ` Adam Sjøgren
2010-08-28 21:40         ` Lars Magne Ingebrigtsen
2010-08-28 23:54           ` Steinar Bang
2010-08-29  0:07             ` Lars Magne Ingebrigtsen
2010-08-29 13:36             ` Adam Sjøgren
2010-08-28 23:50       ` 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=m3wrrasctn.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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).