From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] (Double/guarded) keypress to show all threads
Date: Sat, 12 Jan 2008 21:30:16 -0800 [thread overview]
Message-ID: <1200201168-sup-5812@south> (raw)
In-Reply-To: <1200071751-sup-5552@tomsk>
Excerpts from Marcus Williams's message of Fri Jan 11 09:20:58 -0800 2008:
> This patch adds a multi key combination to expand the thread index
> view to all available threads. Note that this could return _a lot_ of
> threads, which is why I've used a double keypress '!!' as a guard to
> accidental usage. Its useful in conjunction with the tag all and apply
> to all commands though.
This does make me a little nervous. Is the use case always that you want
to apply a command to all threads for a given search? If so, I wonder if
it would be better to explicitly model that, without the intermediate
process of loading all the threads.
If we're going to have a potentially long-running activity like this
available from the UI, then I'd prefer to do it in a manner that gives
the user an indication of how long until completion, the ability to
abort, etc.
How does gmail handle this type of thing? Or is everything so fast with
gmail that it doesn't matter?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-13 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 17:20 Marcus Williams
2008-01-13 5:30 ` William Morgan [this message]
2008-01-13 15:57 ` Nicolas Pouillard
2008-01-13 18:16 ` Marcus Williams
2008-01-14 1:06 ` William Morgan
2008-01-14 10:54 ` Marcus Williams
2008-01-15 4:49 ` William Morgan
2008-01-15 12:29 ` [sup-talk] [PATCH] Search all threads with option to cancel Marcus Williams
2008-01-16 4:30 ` William Morgan
2008-01-16 10:47 ` Marcus Williams
2008-01-16 21:09 ` William Morgan
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=1200201168-sup-5812@south \
--to=wmorgan-sup@masanjin.net \
/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