From: Dave Abrahams <dave@boostpro.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: ding@gnus.org
Subject: Re: Crazy imap unread counts
Date: Fri, 15 Jul 2011 13:55:44 -0400 [thread overview]
Message-ID: <m2fwm7ctsv.fsf@boostpro.com> (raw)
In-Reply-To: <m21uxrschp.fsf@igel.home> (Andreas Schwab's message of "Fri, 15 Jul 2011 19:02:58 +0200")
on Fri Jul 15 2011, Andreas Schwab <schwab-AT-linux-m68k.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
>> To try to get a handle on the most annoying issue (unread counts in the
>> two-hundred-thousands), I started looking where article numbers are
>> persisted: in .newsrc.eld. Below is the part of my gnus-newsrc-alist
>> that refers to INBOX. As you can see, there's a range of article
>> numbers
>>
>> (35583 . 250593)
>
> This is part the range of read articles (there are a lot of holes in
> that range).
I know that's what it means. But I daresay I've never *actually* had article
numbers that high in this mailbox, so it's not clear where it could have
come from.
>> and (gnus-active "INBOX") is
>>
>> (32470 . 250593)
>
> This is coming from the active entry.
Yes, I know where it comes from, although in this case I don't know what
the active entry means.
Eventually, by removing the group, trashing all the agent files, getting
gnus to save the .newsrc.eld file, restarting emacs, and re-adding the
group, I was able to get everything back in synch again. That said,
since *all the information I needed actually lives on the IMAP server*,
there oughtta be a way to do this kind of thing from within Gnus.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-07-15 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 1:21 Dave Abrahams
2011-07-15 17:02 ` Andreas Schwab
2011-07-15 17:55 ` Dave Abrahams [this message]
2011-07-19 17:01 ` Lars Magne 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=m2fwm7ctsv.fsf@boostpro.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=schwab@linux-m68k.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).