From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: gnus-topic-get-new-news-this-topic grabs a lot of data on gnus.ding
Date: Tue, 31 Jul 2001 09:20:24 -0400 [thread overview]
Message-ID: <vxkzo9l2q1z.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <ud76h5jo3.fsf@cli.de> (Christoph Conrad's message of "Tue, 31 Jul 2001 15:10:04 +0200")
Christoph Conrad <cc@cli.de> writes:
> Gnus grabs about 20-30 KByte data
> (shown in the status line) from the server, even when only one or two
> messages with about 2-4 KByte are new.
If `gnus-fetch-old-headers' is non-nil:
*Non-nil means that Gnus will try to build threads by grabbing old headers.
If an unread article in the group refers to an older, already read (or
just marked as read) article, the old article will not normally be
displayed in the Summary buffer. If this variable is non-nil, Gnus
will attempt to grab the headers to the old articles, and thereby
build complete threads. If it has the value `some', only enough
headers to connect otherwise loose threads will be displayed. This
variable can also be a number. In that case, no more than that number
of old headers will be fetched. If it has the value `invisible', all
old headers will be fetched, but none will be displayed.
The server has to support NOV for any of this to work.
next prev parent reply other threads:[~2001-07-31 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 13:10 Christoph Conrad
2001-07-31 13:20 ` Karl Kleinpaste [this message]
2001-07-31 14:44 ` Christoph Conrad
2001-08-17 9:52 ` Lars Magne Ingebrigtsen
2001-08-17 11:37 ` Christoph Conrad
2001-08-17 11:38 ` Christoph Conrad
2001-08-17 12:07 ` Lars Magne Ingebrigtsen
2001-08-17 12:44 ` Christoph Conrad
2001-08-17 13:05 ` Lars Magne Ingebrigtsen
2001-08-17 13:32 ` Christoph Conrad
2001-08-17 13:36 ` Lars Magne Ingebrigtsen
2001-08-17 14:16 ` Christoph Conrad
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=vxkzo9l2q1z.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.com \
/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).