From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] On making kill-thread easier
Date: Thu, 20 Aug 2009 16:43:08 -0400 [thread overview]
Message-ID: <1250800965-sup-4218@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1250797598-sup-5105@tiger.alporthouse.com>
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090820/1dbd06f5/attachment.bin>
next prev parent reply other threads:[~2009-08-20 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 17:07 Carl Worth
2009-08-20 18:19 ` Andrei Thorp
2009-08-20 20:01 ` Chris Wilson
2009-08-20 20:36 ` Andrei Thorp
2009-08-20 21:07 ` Carl Worth
2009-08-20 20:43 ` Ben Walton [this message]
2009-08-20 21:11 ` Carl Worth
2009-08-20 22:56 ` Ben Walton
2009-08-21 0:09 ` Carl Worth
2009-08-21 1:36 ` Carl Worth
2009-08-21 15:16 ` Chris Wilson
2009-08-21 15:19 ` Edward Z. Yang
2009-08-21 15:20 ` Ben Walton
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=1250800965-sup-4218@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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