From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: IMAP and IDLE...
Date: Wed, 16 Mar 2011 13:48:21 -0500 [thread overview]
Message-ID: <87y64eucju.fsf@lifelogs.com> (raw)
In-Reply-To: <m3y64faryq.fsf@quimbies.gnus.org>
On Wed, 16 Mar 2011 18:35:41 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I'd need a count and to be able to peek at the sender and subject of the
>> INBOX, plus to be able to dump the INBOX messages' body text (without
>> attachments) in a temp buffer. So I can say "oh there's mail... let me
>> peek... no, it's not worth splitting it yet." This is how I work now.
LMI> Right, a count might be nice... I'll keep it in mind when (or if) I
LMI> tackle the IDLE issue.
LMI> So far, there's three use cases for idling on INBOX:
LMI> 1) Pull down and split everything there
LMI> 2) For server-side splits, just update the INBOX group -- the
LMI> interesting mail is in the INBOX
LMI> 3) Just report the number of unsplit messages in INBOX, so that it can
LMI> be acted on manually
Maybe a nnimap backend variable of "IDLE-handler" would be nice. It
would receive a list of the new raw message bodies and then the user can
decide what to do by customizing that handler. So we can provide
pre-defined defaults:
for (1), 'run-splits
for (2), 'update-INBOX
for (3), a custom lambda or symbol
That way you can implement the IDLE functionality without worrying about
writing all the rest of the code immediately.
Ted
next prev parent reply other threads:[~2011-03-16 18:48 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 [this message]
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
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=87y64eucju.fsf@lifelogs.com \
--to=tzz@lifelogs.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).