Batch IMAP jobs?

Batch IMAP jobs?

[mikael.svahnberg]

Hi,

I primarily use gnus to read my gmail, and one of the things I like is the ability to quickly and easily mark all the mails that I don't want/need to read and move them away from the inbox (to be compatible with other mail readers e.g. on my phone, I can't just keep them as old articles and let gnus simply not show them).

Any given morning this means that I select 10-20 messages and execute a move command. This is a slow operation and may sometimes take a couple of minutes.

I have a sneaking suspicion (no proof, though) that gnus/nnimap issues one move command per message.

(a) is this true?

(b) if (a), is there a way to change this behaviour so that a single move command for all the selected messages is issued?

(c) if (b), would it make any difference on the speed?


On a side note, when I search messages with (M-s), I get the impression that this is done in the same way (i.e. one IMAP search command is issued for each message), so it ought to be possible to speed things up here too...


/Mikael

Re: Batch IMAP jobs?

[Lars Ingebrigtsen]

mikael.svahnberg@gmail.com writes:

> Any given morning this means that I select 10-20 messages and execute
> a move command. This is a slow operation and may sometimes take a
> couple of minutes.
>
> I have a sneaking suspicion (no proof, though) that gnus/nnimap issues
> one move command per message.
>
> (a) is this true?

Yes.  And moving with nnimap (to larger groups, especially) used to be
very slow, but this is fixed in the current git Gnus tree.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/