Re: Gnus slow?

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> In <873bzf6umt.fsf@orebokech.com> Romain Francoise wrote:

> Did you find out why groups are activated twice?

Hmm, the last message I wrote doesn't indeed make sense.  I must
return to an English writing course.  Let me exercise again. :-p

The reason the recent Gnus uselessly issues the GROUP command
for all the subscribed nntp groups is that the nntp marks feature
provides the `nntp-request-update-info' function.  It always
returns a non-nil value.  When executing the `g' command, it is
called by the `gnus-get-unread-articles-in-group' function by
way of the `gnus-request-update-info' function.  If it returns a
non-nil value, the `gnus-activate-group' function is called with
the third argument `t' and the GROUP command is issued.  Before
May 13, `gnus-request-update-info' returned nil because the
`nntp-request-update-info' function didn't exist then.

Anyway, I've installed the change which makes
`nntp-request-update-info' return nil if `nntp-marks-is-evil' is
non-nil.  Please test!

Note that you have to rebuild Gnus rather than replacing nntp.el
with the new one since the function in question is inlined in
some places.