From: Harry Putnam <reader@newsguy.com>
Subject: Possible small bugs
Date: 08 Feb 2001 12:37:12 -0800 [thread overview]
Message-ID: <m3n1bxcaqr.fsf@reader.newsguy.com> (raw)
I may have stumbled across a small bug:
Mini-Bug
====================================================
Conditions: A procmail fed group that contains all incoming mail
when gnus pulls in mail.... here called `prinb'. (nnml backend)
Procmail feeds to prinb.in. Gnus writes to prinb
This group is run through nnmail split rules after I have a quick
look, then respool, after which the group is completely empty.
In group buffer press M-c (`gnus-group-clear-data') on `prinb' (after
respooling). A large number of unread appears (8869). Press `g'
on `prinb'. Several seconds are spent while gnus gets the
non-existent headers. The progress meter showing % read runs until
it hits 100 then stops. Gnus reports `no unread news' and jumps to
next group.
At the time of this cycle the .overview for `prinb' is zero length.
Thoroughly reproducable
What is that all about?
next reply other threads:[~2001-02-08 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 20:37 Harry Putnam [this message]
2001-02-13 4:14 ` ShengHuo ZHU
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=m3n1bxcaqr.fsf@reader.newsguy.com \
--to=reader@newsguy.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).