From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: IMAP and IDLE...
Date: Wed, 16 Mar 2011 09:28:25 -0500 [thread overview]
Message-ID: <87hbb3w35i.fsf@lifelogs.com> (raw)
In-Reply-To: <878vwfxi3d.fsf@gandalf.home.thebuble.org>
On Wed, 16 Mar 2011 15:20:22 +0100 Olivier Sirven <the.slaa@gmail.com> wrote:
OS> On 2011-03-16 14:53:46, Ted Zlatanov <tzz@lifelogs.com> wrote:
>> I'd rather just see a modeline indicator that I have new mail in INBOX.
>> I really don't want Emacs to freeze randomly and "instant" splitting
>> doesn't have much value for me (if it did, I'd be using Procmail or
>> Sieve on the server side).
OS> Sometimes you just don't have the possibility to do server side
OS> splitting and all you can do is to do it on the client side
My point was that instant splitting is not so useful to me with my
current work pattern. That may change.
On Wed, 16 Mar 2011 14:58:04 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> I assume that for people who use client-side splitting, the question "is
LMI> there new mail in INBOX?" can be emulated with 99.7% accuracy by this
LMI> function:
LMI> (defun nnimap-new-mail-p ()
LMI> t)
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.
I'm not suggesting anyone else needs this, but IMHO it's generally useful.
Ted
next prev parent reply other threads:[~2011-03-16 14:28 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 [this message]
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
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=87hbb3w35i.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).