Excerpts from Chris Wilson's message of Thu Aug 20 16:01:10 -0400 2009: > I have a very similar inbox pattern to Carl, a quick pass to remove > uninteresting material before acting upon the rest. To this end, I use > '&' far less frequently than I should, because it's an awkward key > combination to use in conjunction with scrolling + archiving, and so I > am irritated by repeatedly archiving a thread which I have never read. > The behaviour I would like here is exactly: "Shouldn't sup just see that > I'm not ever reading this thread when it reappears?".
I have a similar pattern where there are lots of list messages that I don't care about (based on subject). I skim the inbox using 't' to tag all messages I don't care about. When I've tagged a bunch of items, after the scan, I simply to '=' followed by either 'A' (archive, mark read) or '&'. It saves lots of shift key use and allows me to quickly tackle a lot of mail. > I'd be happy to have sup automatically kill a thread that I have > archived twice without reading. I think this kind of heuristic is a) hard to get right b) not required if you do batch operations as described above. Part b) is subject to personal opinion, of course! :) HTH. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
