Re: gnus uses a cache? And how it affects mairix searches...

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> Dan Christensen <jdc@uwo.ca> writes:
>>
>>> In gnus.el, it doesn't list nnmairix at all, but somehow when using
>>> nnmairix, an entry for nnmairix gets added to this list, without the
>>> virtual keyword (see below).
>>
>> diff --git a/lisp/nnmairix.el b/lisp/nnmairix.el
>> index 0cef699..b2f74e3 100644
>> --- a/lisp/nnmairix.el
>> +++ b/lisp/nnmairix.el
>> @@ -417,7 +417,7 @@ Other back ends might or might not work.")
>>  
>>  (nnoo-define-basics nnmairix)
>>  
>> -(gnus-declare-backend "nnmairix" 'mail 'address)
>> +(gnus-declare-backend "nnmairix" 'mail 'address 'virtual)
>>  
>>  (deffoo nnmairix-open-server (server &optional definitions)
>>    ;; just set server variables
>>
>> Andreas.
>
> After look at this for a while, I do think this is the right solution --
> what do you all think? Can someone apply this change?

Oh never mind, I guess I didn't look long enough. For any backend
declared as virtual, `gnus-cache-possibly-enter-article' will use
`nnvirtual-find-group-art' to get the real group name.

That means that if a backend is declared 'virtual but isn't actually
nnvirtual, the caching mechanism will use the wrong lookup function.

nnir should use `nnir-article-group'

nnmairix could probably do it with a little massaging of
`nnmairix-determine-original-group-from-path'.

What we'd really want is a properly-abstracted nnoo function that
virtual backends would use to locate the real article.

In the meantime, it would probably be enough to make
`gnus-uncacheable-groups' match nnmairix and nnir groups.

Eric