From: Harry Putnam <reader@newsguy.com>
Subject: Something very wrong here
Date: Mon, 03 Sep 2001 19:37:34 -0700 [thread overview]
Message-ID: <m14rqj4r69.fsf@reader.newsguy.com> (raw)
I have a group that recieves all new mail for scanning. Slurped from
a procmail spool. Imagine I delete this group after using it and
respooling all its messages to other groups.
C-u G del <prinb> <gone without a trace>
Or is it?
Close gnus then emacs, restart. Create a group with `G m' from nnml
backend naming it prinb attempt to enter the group:
Now reporting from *Messages* after restarting
Creating mail directory /home/reader/Mail/prinb/ <= create the group
Retrieving newsgroup: nnml:prinb...
Loading gnus-ml (source)...done
Fetching headers for nnml:prinb...
nnml: Receiving headers...done
Fetching headers for nnml:prinb...done
Scoring...done
Loading gnus-async (source)...done
Bootstrapping marks for prinb...
What is all the frenetic activity about? It even shows a percent count
as the non-existent headers are downloaded.
Fictitious group count is generated something like 3000+
Non existent marks are generated for non existent messages.
Finally reporting
No unread news
Do we need all this overhead, in an empty newly created group?
Why is there a fictitious message count generated? Where is the false
info coming from? Can't be .overview, since it is rm'ed.
When a group is C-u G del'ed and gnus is closed, shouldn't that
groups info disappear from newsrc.eld, as well as any `active' file?
next reply other threads:[~2001-09-04 2:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 2:37 Harry Putnam [this message]
2001-09-04 13:47 ` Kai Großjohann
2001-09-04 14:38 ` Simon Josefsson
2001-09-04 16:12 ` Harry Putnam
2001-09-04 17:54 ` Kai Großjohann
2001-09-05 2:58 ` Harry Putnam
2001-09-05 10:02 ` Kai Großjohann
2001-09-04 19:08 ` Simon Josefsson
2001-09-05 20:03 ` Harry Putnam
2001-09-05 20:29 ` Simon Josefsson
2001-09-05 22:47 ` Harry Putnam
2001-09-05 23:42 ` Harry Putnam
2001-09-05 21:45 ` Kai Großjohann
2001-09-05 22:13 ` Harry Putnam
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=m14rqj4r69.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).