From: dsg@mitre.org (David S. Goldberg)
Subject: Re: Unwanted catchup when entering a newsgroup
Date: 11 Oct 1999 10:15:08 -0400 [thread overview]
Message-ID: <m1bemf2nfv7.fsf@blackbird.mitre.org> (raw)
In-Reply-To: piet@cs.uu.nl's message of "11 Oct 1999 10:32:29 +0200"
>>>>> Florian Weimer <fw@deneb.cygnus.argh.org> (FW) writes:
>>> From time to time, Gnus marks as read all articles of a newsgroup
FW> when I try to enter this group (and doesn't show the summary
FW> buffer). After that, the unread article count is zero. This
FW> happens only very sporadically, and I haven't been able to track
FW> it down yet. Any ideas? I haven't observed this with v0.96 or
FW> mail groups, BTW.
> I have observed the same. I just went back to the official gnus
> version (5.6.45) and looked in those newsgroups and found no
> messages that I had missed. So my guess is that pgnus just makes an
> error in the initial article count.
I've seen that as well. I've also found on occasion that my scoring
rules end up catching up the entire group. I use adaptive scoring
with an expunge and duplicate suppression as well as some aggressive
manual scoring. Still, I find it a bit disconcerting when an entire
days worth of news is eliminated that way. I find a fairly easy, if
time consuming for certain groups, check is to do a C-u 0 M-RET on the
group. That gives me an empty summary buffer. Since I ordinarily use
threading, I do a T T to turn threading off and then a C-c C-s C-n to
sort by article number. I haven't yet found anything at the end of
that buffer that I actually wanted to read anyway.
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next prev parent reply other threads:[~1999-10-11 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-09 7:37 Florian Weimer
1999-10-09 14:22 ` Ted Rathkopf
1999-10-09 15:01 ` Florian Weimer
1999-10-11 8:32 ` piet
1999-10-11 14:15 ` David S. Goldberg [this message]
1999-10-11 13:14 piet
1999-10-12 15:29 ` piet
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=m1bemf2nfv7.fsf@blackbird.mitre.org \
--to=dsg@mitre.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).