Re: Automatically marking Gcc's as SEEN in nnimap

[Lloyd Zusman <ljz@asfast.com>]

David Engster <deng@randomsample.de> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
>>
>> [ ... ]
>>
>> Furthermore, immediately after this command completes, the articles seem
>> to be marked as SEEN (or at least they are not flagged as unread/unseen
>> in the *Summary* buffer).  However, if I then run a
>> `gnus-group-get-new-news', the unread/unseen mark returns, and I can
>> only make it go away by actually reading the article.
>
> I would guess this behavior comes from gaps in the article numbers. This
> problem can't currently properly dealt with and also depends on the used
> IMAP server. Does doing M-g on that group fix the number?

Yes, `M-g' fixes it.


>> [ ... ]
>
> No, they don't get re-propagated to the IMAP server. Gnus simply doesn't
> have all the necessary information for correctly calculating the number
> of unread articles. When you do gnus-group-get-new-news, Gnus will try
> to determine the number of unread articles purely based on the active
> information (ie. lowest and highest article number in a group), and on
> the group info, which contains the article numbers of already seen
> articles. When you do M-g on a group, it will also re-scan the group on
> the server, which can sometimes correct this problem.

OK. This explains and fixes the problem.

So do you see any disadvantage to my writing some function that runs
`gnus-group-get-new-news-this-group' (`M-g') on each of my groups, and
then rebinding this function to `g' (currently bound to
`gnus-group-get-new-news')?  It seems like such a function would be
more useful, especially for nnimap groups.

In any case, thanks for all your help!


-- 
 Lloyd Zusman
 ljz@asfast.com
 God bless you.