From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] On making kill-thread easier
Date: Thu, 20 Aug 2009 18:56:52 -0400 [thread overview]
Message-ID: <1250808931-sup-3198@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1250802452-sup-4348@yoom.home.cworth.org>
Excerpts from Carl Worth's message of Thu Aug 20 17:11:49 -0400 2009:
> 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 typically do a big pass to 'A' or '&' large numbers of things. That
knocks the list to a point where I can either do another smaller pass
where I'll apply labels and skim things. My last pass is for things I
actually read, many of which get archived right away too. I don't
completely practice 'inbox 0' but I do follow many of its tenets.
My own personal habits are such that an archived thread has to really
bug me before I kill it, so much of the first (morning) pass is for
'A.' Part of this is because while I don't want to necessarily follow
a thread, there is potential for interesting things to pop in late in
the game (many of these are on the git ml)...so, after I see a lot of
activity on it, I may scan the thread or possibly read it.
Bike shedding gets killed quickly! :)
> 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. :-)
If you get into adding code, consider writing it such that there is an
available Hook that overrides the default behaviour. This may get you
the best of all outcomes. It'd be useful for you and more likely to
be useful for others.
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/0226132d/attachment.bin>
next prev parent reply other threads:[~2009-08-20 22:56 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
2009-08-20 21:11 ` Carl Worth
2009-08-20 22:56 ` Ben Walton [this message]
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=1250808931-sup-3198@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