From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: nnimap unread count broken again
Date: Thu, 21 Oct 2010 07:20:02 -0400 [thread overview]
Message-ID: <m3sjzzyepx.fsf@jhcloos.com> (raw)
In-Reply-To: <m3tykj9smz.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 18 Oct 2010 22:02:12 +0200")
I seem to have lost the article I wanted to reply to, but this is in the
right thread....
The article counts seem to be correct, now, after a M-g, but not after g.
I do make frequent use of the cache to backup stuff which is interesting;
might that interfere with the unread counts?
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-10-21 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 10:05 Frank Schmitt
2010-10-18 10:36 ` Steinar Bang
2010-10-18 10:47 ` Frank Schmitt
2010-10-18 11:01 ` Steinar Bang
2010-10-18 16:42 ` Dave Goldberg
2010-10-18 19:55 ` Lars Magne Ingebrigtsen
2010-10-18 19:25 ` Lars Magne Ingebrigtsen
2010-10-18 19:57 ` Frank Schmitt
2010-10-18 20:01 ` Lars Magne Ingebrigtsen
2010-10-18 20:02 ` Lars Magne Ingebrigtsen
2010-10-18 20:13 ` Frank Schmitt
2010-10-18 21:02 ` Dave Goldberg
2010-10-21 11:20 ` James Cloos [this message]
2010-10-21 16: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=m3sjzzyepx.fsf@jhcloos.com \
--to=cloos@jhcloos.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).