From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: entering nndir without .overview retrieves each article twice.
Date: 02 Nov 1995 04:40:47 +0100 [thread overview]
Message-ID: <w8slopzadkw.fsf_-_@surt.ifi.uio.no> (raw)
In-Reply-To: Robert Nicholson's message of Mon, 30 Oct 1995 13:43:40 -0800 (PST)
In-Reply-To: Robert Nicholson's message of Mon, 30 Oct 1995 13:43:40 -0800 (PST)
Robert Nicholson <robert@steffi.accessone.com> writes:
> When there is no .overview file in an nndir group should gnus retrieve
> each article twice upon entering the group?
Probably. It tries to read the head of the articles in 1k gulps.
(Most heads are less than 1k.) `nnheader-insert-head' reads until it
finds a blank line, or it has read 4k, whichever comes first.
In fact, I've never tried whether the current implementation is any
faster than just inserting the entire file into the buffer and
removing the body. Does anybody feel up to doing some timings?
--
Home is where the cat is.
parent reply other threads:[~1995-11-02 3:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <199510302143.NAA03031@steffi.accessone.com>]
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=w8slopzadkw.fsf_-_@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).