On Sunday, May 4, 2008 9:02pm, Daniel Wagner <[EMAIL PROTECTED]> said:
> 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. Which reminds me that, as of 0.5 release, the bug I reported about &-killed threads reappearing is still present. But, other than that, 0.5 is a treat. Cheers, Kendall _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
