From: * Tong * <sun_tong@users.sourceforge.net>
Subject: Gnus, # of headers to retrieve
Date: 15 Jan 2003 17:51:18 -0500 [thread overview]
Message-ID: <sa8k7h6do2h.fsf@suntong.personal.users.sourceforge.net> (raw)
Hi,
I think there might be a bug when Gnus decides how many of news
headers to retrieve.
When entering a big newsgroup, Gnus will prompt me something like
"number of headers to retrieve". No matter how little I specified,
Gnus will always retrieve the whole list first, then show me the
number of messages I specified, with '{50 (+264714 more)}' showing
on the status bar.
This does not bother me previously, but currently I'm on a dial up
networking, with the news server happens to carry huge postings. To
give you an idea how big it is:
375094( 28): comp.os.linux.misc (0)
26844( 5): comp.os.linux.security (0)
264852( 1): comp.os.linux.setup (0)
131964( 5): comp.os.linux.x (0)
The headers for comp.os.linux.setup e itself is over 3M, and
retrieving it seems forever for me (;->). What worse is that I have
to pay for those extra downloads that I don't need (and see). :-(
Ok, quite a long bug report but quite an easy fix. Hope the new
version of gnus will issue the xover command according to
gnus-large-newsgroup (or the user specification), to limit the
header download, and not retrieving the whole list.
Thanks
PS. My Gnus comes with RH8:
Gnus v5.9.0
GNU Emacs 21.2 (i686-pc-linux-gnu, X toolkit)
200 Bell Nexxia News Server (Twister v1.2.0)
PPS. A side request,
It'd be quite nice to have some local caching capabilities for dial
up Internet access like me.
What I was looking in the gnus info manual (but not found) were the
capabilities to cache
- the subscribed newsgroup headers
- and viewed articles.
So that they don't need to be retrieved again, once that have been
downlaoded. Surely a proper expiration mechanism is also need for
that.
thanks
--
Tong (remove underscore(s) to reply)
*niX Power Tools Project: http://xpt.sourceforge.net/
- All free contribution & collection
next reply other threads:[~2003-01-15 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 22:51 * Tong * [this message]
2003-01-16 18:02 ` Lars Magne Ingebrigtsen
2003-01-17 6:57 ` u.r. faust
2003-01-19 6:08 ` * Tong *
[not found] ` <84hec914ek.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <87lm16t620.fsf@dingbat.katzenjammer.org>
2003-01-28 7:12 ` Kai Großjohann
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=sa8k7h6do2h.fsf@suntong.personal.users.sourceforge.net \
--to=sun_tong@users.sourceforge.net \
/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).