Gnus development mailing list
 help / color / mirror / Atom feed
From: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>
To: ding@gnus.org
Subject: Re: IMAP IDLE command
Date: Wed, 01 Dec 2010 02:05:30 +0100	[thread overview]
Message-ID: <87wrnu2tgl.fsf%lukasz.stelmach@iem.pw.edu.pl> (raw)
In-Reply-To: <87sjyj24iz.fsf@pcuds33.cern.ch>

Tibor Simko <tibor.simko@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




  reply	other threads:[~2010-12-01  1:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 17:09 Łukasz Stelmach
2010-11-28 17:31 ` Byung-Hee HWANG
2010-11-28 21:21   ` Łukasz Stelmach
2010-11-28 21:23   ` Łukasz Stelmach
2010-11-29  4:36 ` Lars Magne Ingebrigtsen
2010-11-29  5:10   ` Daniel Pittman
2010-11-29  6:21     ` Łukasz Stelmach
2010-11-29  7:38       ` Frank Schmitt
2010-11-29 21:25         ` Łukasz Stelmach
2010-11-29 21:37           ` Dan Christensen
2010-12-14 23:20     ` Ted Zlatanov
2010-12-15 19:34       ` Lars Magne Ingebrigtsen
2010-12-15 21:04         ` Ted Zlatanov
2010-11-29 21:39   ` Tibor Simko
2010-12-01  1:05     ` Łukasz Stelmach [this message]
2010-12-01  8:50       ` Steinar Bang
2010-12-02  0:12         ` Łukasz Stelmach
2010-12-02  9:07           ` Steinar Bang
2010-12-02 10:19             ` Łukasz Stelmach
2010-12-02 13:29               ` Steinar Bang
2010-12-02 18:25                 ` Łukasz Stelmach
2010-12-02 13:37               ` Julien Danjou
2010-12-02 18:13                 ` Łukasz Stelmach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wrnu2tgl.fsf%lukasz.stelmach@iem.pw.edu.pl \
    --to=lukasz.stelmach@iem.pw.edu.pl \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).