Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Sean McAfee <eefacm@gmail.com>
To: info-gnus-english@gnu.org
Subject: w3m renderer is exceedingly slow on large message
Date: Tue, 19 Oct 2010 10:51:08 -0700	[thread overview]
Message-ID: <bp8bp6qjckz.fsf@usca1uw-JZWWPM1.sanmateo.corp.akamai.com> (raw)

I've recently started using Gnus to read my mail at work.  A few times a
day I get sent somewhat large HTML documents, typically around 800Kb in
size, containing mostly tables.  With mm-text-html-renderer set to w3m,
Gnus takes upwards of thirty seconds to render these messages.  Is that
supposed to happen?  If I save the message and apply the w3m program to
it on the command line, it finishes in less than a second.

I just now tried setting the renderer to w3m-standalone, and now the
large messages render quickly, but as plain text, without hyperlinks,
coloring, or fancy table borders.

             reply	other threads:[~2010-10-19 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 17:51 Sean McAfee [this message]
2010-10-19 18:09 ` Lars Magne Ingebrigtsen

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=bp8bp6qjckz.fsf@usca1uw-JZWWPM1.sanmateo.corp.akamai.com \
    --to=eefacm@gmail.com \
    --cc=info-gnus-english@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.
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).