Gnus development mailing list
 help / color / mirror / Atom feed
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Subject: Re: gnus-summary-tick-article-forward
Date: Fri, 02 Feb 1996 15:01:24 -0600	[thread overview]
Message-ID: <199602022101.PAA17047@sina.hpc.uh.edu> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 02 Feb 1996 21:01:51 +0100

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

LMI> The articles are only fetched if you use the cache.  Ticked articles
LMI> are fetched so they can be entered into the cache.

I can understand why they're being fetched, but why do they have to be
displayed (and highlighted and decoded and everything else)?  This can take
a *long* time for big articles.

For testing speed in extreme cases, I just go to alt.binaries.games.  It
has incredibly high traffic (1000+ messages/day) and really huge articles
(15000 lines).  It also stress-tests the uudecoding code.

 - J<


      reply	other threads:[~1996-02-02 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-01 16:07 gnus-summary-tick-article-forward Jack Vinson
1996-02-02 20:01 ` gnus-summary-tick-article-forward Lars Magne Ingebrigtsen
1996-02-02 21:01   ` Jason L Tibbitts III [this message]

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=199602022101.PAA17047@sina.hpc.uh.edu \
    --to=tibbs@hpc.uh.edu \
    --cc=tibbs@uh.edu \
    /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).