Re: slow nnimap moves due do many SELECTs

[Ted Zlatanov <tzz@lifelogs.com>]

On Thu, 30 Sep 2010 18:43:31 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> I'm leaning towards 2)...

LMI> Or option pi), which I've now implemented: Use EXAMINE instead of
LMI> SELECT.  On some servers EXAMINE is a lot faster.  Could you try it and
LMI> see whether this helps at all?

Yes, that's a bit faster.  SELECT does a lot more so that makes sense;
is there any downside to EXAMINE?

On Thu, 30 Sep 2010 19:02:48 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:

>> Why not use the LAST parameter to nnimap-request-move-article to
>> trigger the group update?  It's only set for the last article in the
>> list AFAICT.

LMI> I don't really want to rewrite all the backend -move and -accept
LMI> methods.  There must be at least ten of them...

I don't understand.  The LAST parameter is already there and given to
you by Gnus (it's t only for the last article) when the user runs `B m',
right?

Ted