Re: nnimap unread count broken again

[Dave Goldberg <david.goldberg6@verizon.net>]

>>>>> Frank Schmitt <ich@frank-schmitt.net>:
>> Hmm. Isn't this removing symptoms instead of curing the disease?

> I presume that if you start new gnusen with clean .newsrc.eld files, and
> start subscribing to the groups in question you will never see the
> issue...? 

> The way I understood it, what you're seeing is caused by the .newsrc.eld
> files being out of sync, and M-g'ing the group is a way of synching
> them.

> Once they are synched you shouldn't have the issue.

> Again, the way I've understood it, this is a result of the way QRESYNC
> implementation tries to keep the network traffic to a minimum (and
> thereby the speed to a maximum).

I only use one instance of Gnus, and no, the count never resync's by running M-g on the group line.  I've sent Lars (directly per his instruction due to the size) the traces I got through debugging and hopefully that will help to resolve the problem.  Can say for certain that James Cloos is correct that the count has gone back to being determined by subtracting the smallest UID number from the highest.  On my cyrus server this actually works because the UIDs are consecutive.  On Exchange the numbers can be quite bizarre (a group with two unread showed over 100 in the Group buffer).  As I've noted in earlier posts, watching the IMAP traffic, the server is clearly providing the correct numbers; Gnus is no longer doing the right thing with them as it did up until a week or so ago.  I've tried
  to look at git bisect per someone's suggestion but am sufficiently unfamiliar with git that I've been unable to get anywhere.

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net