Re: 'g' not checking nnimap groups

[Simon Josefsson <jas@extundo.com>]

gdt@work.lexort.com writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Actually, the bug is how (nnimap "foo") ever got into your setup.
>
> I agree that's a bug.  I think I did U and then subscribed to a group,
> before I realized the preferred way was to use server mode and browse.

I've tried that, and I can't seem to reproduce it.  But others have
said similar things.  Maybe it only happens sometimes.

>> The server (nnimap "foo") isn't the same as (nnimap "foo" (nnimap-port
>> ...) ...), and Gnus will treat them as different servers.
>> Consequently, (nnimap "foo") is treated as an ephemeral server, and
>> checked using the slow mechanism (I forgot the reason as to why, but
>> it is probably because it is simpler to optimize the primary/secondary
>> case).
>
> But, gnus used the same imap server connection.  The "foo" in the
> wrong group spec isn't the same as the IMAP server, so it must have
> used the nnimap select method in gnus-secondary-select-methods to find
> it.

Actually, I think Gnus doesn't, but nnimap then locate the same server
connection using the server name only.

But it was a long time since I looked at this in detail, so I could be
wrong, and the only way to find out is to play with edebug and see
what happens.

> On my list of things to look into if I find spare time:
>
>   add path from UNSEEN count from STATUS to count of new articles in
>   summmary
>
>   investigate nnimap/agent cache coherency, ensuring articles
>   deleted/moved by other clients are removed from the agent.

Fixing those would be very good, many people have problems related to
similar issues.  I don't think fixing them is that complicated.