From: Wes Hardaker <wes@hardakers.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: IMAP and IDLE...
Date: Thu, 17 Mar 2011 11:08:20 -0700 [thread overview]
Message-ID: <sdpqpptyaz.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <87r5a7yvv6.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 16 Mar 2011 14:37:33 +0000")
>>>>> On Wed, 16 Mar 2011 14:37:33 +0000, Eric S Fraga <e.fraga@ucl.ac.uk> said:
ESF> I long ago got rid of any biff type functionality in my system as
ESF> there was no point. on that note, I don't need any automatic
ESF> loading of email; I'm happy to git 'g' when *I* want to read
ESF> email... but that's me.
The trick to this is server-side-splitting with a biff system that can
watch and prioritize multiple boxes. I ended up writing yet-another new
biff system (qmailcheck) that color codes "new" lines in it, displays
things by a prioritized list of folders so that the important ones are
at the top (and I concentrate on them). Only some mailboxes cause the
window to pop forward and others (really important) issue task-bar
notifications. The ding list doesn't even get listed in it (sorry
Lars). If I had a single INBOX, you're right, biff would be useless.
So, the trick to mail (and I get tons) is still server-side-filtering.
I cringe at the thought of everyone doing client side filtering and
watching it all get sucked in and then filtered as they wait.
--
Wes Hardaker
My Pictures: http://capturedonearth.com/
My Thoughts: http://pontifications.hardakers.net/
next prev parent reply other threads:[~2011-03-17 18:08 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 [this message]
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
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=sdpqpptyaz.fsf@wjh.hardakers.net \
--to=wes@hardakers.net \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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).