Excerpts from Ben Walton's message of Thu Aug 20 13:43:08 -0700 2009: > Excerpts from Chris Wilson's message of Thu Aug 20 16:01:10 -0400 2009: > 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.
Thanks, Ben! This is just the kind of workflow report I've been hoping to read. I wonder, though, what happens when you want to archive some and kill others. Do you end up making two passes? Executing the '=' operation partway through and then start tagging again? A quick, non-tag 'A' or '&' for the exceptional thread? Or maybe just let a few slip by the "wrong" direction. > > 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! :) I plan to try a single keybinding for archive-or-kill-if-unread for a while and see how I like it, (I'll obviously share it when I code it up).. Of course, the failure mode is hiding messages from me, so it might be hard for me to know if it fails. :-) -Carl
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
