From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: nnml group has move messages than gnus sees
Date: Sun, 24 Aug 2014 17:01:36 -0400 [thread overview]
Message-ID: <87lhqd4n67.fsf@reader.local.lan> (raw)
I should know how to do this and seem to recall having done it at some
time in the past. That is:
Make gnus `see' messages in a (nnml) group that are not showing up by
normal means.
Gnus `sees' 1459 messages in nnml:all
ls sees 6409 in ~/Mail/all
I ran
M-x: nnml-generate-nov-databases-directory <RET> ~/Mail/all <RET>
But message count stayed at 1459.
I tried rm Mail/all/.overview
Then nnml-generate-nov-databases-directory
Still no change in count.
So, how to make gnus `see' the other 4500 or so messages?
These messages have been moved around a bit. I rsynced my whole mail
setup from one machine to another a while back but saw no errors or
etc.
However, it may be the case that I am just now noticing the anomally
and it has been there ever since the move.
But in general, how would one go about forcing gnus to recognize the
missing messages?
next reply other threads:[~2014-08-24 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 21:01 Harry Putnam [this message]
2015-01-27 7:19 ` Lars Ingebrigtsen
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=87lhqd4n67.fsf@reader.local.lan \
--to=reader@newsguy.com \
--cc=ding@gnus.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).