Re: ahh... it's the problem noted a few months back

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Simon Josefsson <jas@pdc.kth.se> writes:

> Yes, like Tibor mentioned my hint doesn't help the `2 g' cases. Some
> time ago I traced this into `gnus-get-unread-articles', it falls
> through to the 'update-info' call below. It shouldn't. I don't
> understand the purpose of this code, so it's hard to come up with a
> fix. Perhaps another cond case in the foreign-level could solve this,
> but I'm only guessing here...

Well, the purpose of the code is to update all the groups that should
be updated.  :-)  All non-native, non-secondary groups get checked
individually.

But when Gnus mistakenly takes some groups as foreign instead of
secondary, you get all these gazillion "Reading new mail..."
messages.  So the question is -- why doesn't Gnus realize that these
groups are secondary?

I think.  Could somebody who sees this edebug through this function
and see which `(gnus-activate-group group 'scan)' is doing the dirty
deed?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen