Daniel Wagner wrote:
Excerpts from yanghatespam's message of Sun May 04 17:47:50 -0700 2008:
If sup's thread-grouping is decent, then it would be neat/more accurate
to extend sup somehow to instead use these groupings for the filtering.
I.e., if an incoming message is grouped with a thread in which I was a
participant, then leave it marked unread; otherwise, mark it read.
Well, sup already has a pretty nice (and similar) feature for killing
entire threads. The '&' key will archive a thread permanently; that is,
if new mails arrive in that thread, they will automatically be archived.
So, you can hit '&' once for each thread you don't want to read; the
rest will reappear in you inbox as new mails arrive in them.
It's a bit inverted from what you want, but maybe it will do? In any
case, if you want to extend sup, you should look at how that key works.
I do need to deal with a large volume of mail, so it's not really what
I'm looking for, because (1) I'd be doing this all day long, and (2)
it's error-prone - I can easily kill a relevant thread. BTW, Gmail has
had this feature in the form of the 'm' key (for "mute").
(6) Scrolling through the buffer that is immediately presented to me
when starting sup, I only see about 3 pages of threads. Is this
correct? How do I get to the rest?
The 'M' key will load more threads.
Thanks.
Good luck!
~d
P.S. I'm running a slightly old version of sup, so the actual keys might
not be '&' and 'M' any more. '?' should list the available commands at
any time.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
--
Yang Zhang
http://www.mit.edu/~y_z/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
