1 Dec 2010 02:05
Re: IMAP IDLE command
Łukasz Stelmach <lukasz.stelmach <at> iem.pw.edu.pl>
2010-12-01 01:05:30 GMT
2010-12-01 01:05:30 GMT
Tibor Simko <tibor.simko <at> cern.ch> writes: > On Mon, 29 Nov 2010, Lars Magne Ingebrigtsen wrote: >> Nope. Gnus really doesn't have any sort of mechanism for getting >> updates from the servers asynchronously. But it'd be nice if it did. [...] > A use case would go like this: instead of helping user to decide whether > to do `g' (as in the case of IMAP IDLE), one would do `g' periodically > anyway (e.g. via daemon), and if certain conditions are met for certain > articles, notification would get displayed for each interesting article. > (Could be all incoming ones, could be an interesting subset only.) I don't like the idea of automatic `g' it may work if you've got fat cable and few servers you pull mail from. Today I've got something like five IMAP servers configured and two POP3 accounts and a full `g' takes about 10 seconds if IMAP connections have been closed. I would not be happy with a 10s delay when I am coding. That's why I think IMAP IDLE is such a good thing. If you do not use server side splitting (procmail, sieve etc.) you alway get your inbound mail in the INBOX. There is no need to watch for more than one folder and it is enough you get a flag next to the INBOX group in the *Group* buffer indicating that a new mail is ready for `M-g'. It's quite late here so I won't go furher. -- -- Miłego dnia, Łukasz Stelmach(Continue reading)





RSS Feed