From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] What's your sup workflow (and a spew of ideas)
Date: Tue, 18 Aug 2009 14:46:41 -0700 [thread overview]
Message-ID: <1250631221-sup-8993@yoom> (raw)
In-Reply-To: <1250629282-sup-8521@yoom>
Excerpts from Carl Worth's message of Tue Aug 18 14:02:05 -0700 2009:
> Anyway, I've probably run into several other little things that I
> didn't capture in this email, but I'll hopefully remember them
> later.
And of course, here are a few:
inbox-mode
----------
* [dont-perturb-selected-thread-when-new-mail-arrives]
I think I just saw the following race condition:
1. I have the top-most thread selected and I identify it as spam
2. I start moving to press the d key to delete it
3. Before I get their, new mail arrives and becomes selected
4. I delete mail I really care about
I propose that new mail arriving should not cause the selector to
move from the thread currently selected.
label-list-mode
---------------
* [allow-for-limiting-to-interesting-labels]
In the workflow I described earlier, I process all mail mercilessly
and get it archived and out of my inbox as quickly as possible. But
some of those threads I identified as needing some significant time
to deal with, so I labelled them to assign them to a particular
"project".
So, later, I'd like to look at my list of projects, choose one, and
then choose the first task to be done.
The label-list-mode is *almost* the perfect thing for this. The
only problem is that it displays several labels, (with *lots* of
messages each) that are not interesting to me at all in this
sense. For example, killed and unread, for example, as well as
several other labels that I use in ways other than my "project"
labels.
What I'd like here is a feature much like 'u' which toggles to
display of only labels with unread messages, but insteads toggles
to display only the labels that I've somehow marked as my "project"
labels. (I'm not sure exactly how to name this feature for general
use. The "project" sense is something personal to my usage. Maybe,
"todo" or something?)
inbox-mode/search-result-mode
-----------------------------
* [display-number-of-unread-messages]
In my ruthless scan while processing new messages, I want to be able
to make split-second, yet accurate, decisions on whether I need to
read messages, (and if so, how much time it will take). The current
thread display shows a total number of messages within a thread, but
that leads to me making an inaccurate estimate of how "expensive" it
would be to read a thread. I'd much rather see the number of unread
messages in the thread. Perhaps best would be to diplay both numbers
such as: (1/64) with the 1 in bold to indicate that a thread with 64
total messages has 1 unread message.
-Carl
-------------- 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/20090818/5f65c5b3/attachment.bin>
next prev parent reply other threads:[~2009-08-18 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 21:02 Carl Worth
2009-08-18 21:46 ` Carl Worth [this message]
2009-08-18 22:07 ` Andrei Thorp
2009-08-18 22:16 ` Carl Worth
2009-08-18 23:02 ` Rich Lane
2009-08-19 1:58 ` Carl Worth
2009-08-19 3:02 ` Rich Lane
2009-08-19 14:03 ` Andrei Thorp
2009-08-19 23:21 ` Carl Worth
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=1250631221-sup-8993@yoom \
--to=cworth@cworth.org \
/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