From: Olivier Sirven <the.slaa@gmail.com>
To: ding@gnus.org
Subject: Re: IMAP and IDLE...
Date: Wed, 16 Mar 2011 15:13:00 +0100 [thread overview]
Message-ID: <87hbb3xifn.fsf@gandalf.home.thebuble.org> (raw)
In-Reply-To: <m3wrjzjo97.fsf@quimbies.gnus.org>
On 2011-03-16 12:31:00, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> But here's my idea: We could open an extra connection to every IMAP
> server (that we're doing client splits on). We issue an IDLE on the
> INBOX. If the connection goes away, we don't do anything asynchronously.
> But otherwise, every time we get a new message in the INBOX, we run it
> through the normal splitting methods and update the group buffer.
>
> Since this will mostly be splitting one single message at a time, and we
> only download the headers to do the splitting, this can probably be done
> without hanging Emacs too badly.
It would be a great feature to have (at least for me).
I receive about 5K/6K mails a day in my IMAP INBOX and it's a real pain
each time I refresh my group buffer. During work days I do it manually
(maybe once every 10mn) and I have to wait for 1mn before being able to
use my emacs again. I coded an autochecker to do it automatically every
5mn that I can easily launch when I need to because after 2 days without
any refresh I would have to wait for 5mn before being able to use emacs
again (that time drastically went down with the new nnimap
implementation though).
So if I can just drop that macro and have an async gnus checking my
emails and doing the splitting word everytime I receive a new email and
leaving my emacs usable it would be just the best thing in the world ;)
That being said it would be quite useful to be able to specify the list
of IMAP folders that needs an IDLE command to be issued from time to
time.
--
Olivier
next prev parent reply other threads:[~2011-03-16 14:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 11:31 Lars Magne Ingebrigtsen
2011-03-16 11:43 ` Greg Troxel
2011-03-16 13:46 ` Frank Schmitt
2011-03-16 13:53 ` Ted Zlatanov
2011-03-16 13:58 ` Lars Magne Ingebrigtsen
2011-03-16 14:37 ` Eric S Fraga
2011-03-17 18:08 ` Wes Hardaker
2011-03-17 18:31 ` Ted Zlatanov
2011-03-17 20:52 ` Wes Hardaker
2011-03-17 21:04 ` Ted Zlatanov
2011-03-18 8:51 ` Eric S Fraga
2011-03-18 14:36 ` Wes Hardaker
2011-03-18 16:00 ` Eric S Fraga
2011-03-19 0:28 ` Wes Hardaker
2011-03-21 10:57 ` Julien Danjou
2011-03-21 14:15 ` Eric S Fraga
2011-03-16 14:20 ` Olivier Sirven
2011-03-16 14:28 ` Ted Zlatanov
2011-03-16 17:35 ` Lars Magne Ingebrigtsen
2011-03-16 18:48 ` Ted Zlatanov
2011-03-17 17:18 ` Lars Magne Ingebrigtsen
2011-03-17 17:31 ` Ted Zlatanov
2011-03-17 17:44 ` Lars Magne Ingebrigtsen
2011-03-17 18:24 ` Ted Zlatanov
2011-03-16 14:13 ` Olivier Sirven [this message]
2011-03-16 17:37 ` Lars Magne Ingebrigtsen
2011-03-16 18:28 ` Olivier Sirven
2011-03-16 18:34 ` David Engster
2011-03-17 18:11 ` Wes Hardaker
2011-03-17 18:14 ` Lars Magne Ingebrigtsen
2011-03-17 20:53 ` Wes Hardaker
2011-03-29 19:14 ` Lars Magne Ingebrigtsen
2011-03-16 20:21 ` John Sullivan
2011-03-17 17:19 ` Lars Magne Ingebrigtsen
2011-03-17 20:30 ` James Cloos
2011-03-29 19:13 ` Lars Magne Ingebrigtsen
2011-04-01 23:11 ` John Sullivan
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=87hbb3xifn.fsf@gandalf.home.thebuble.org \
--to=the.slaa@gmail.com \
--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).