From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] (Double/guarded) keypress to show all threads
Date: Sun, 13 Jan 2008 18:16:12 +0000 [thread overview]
Message-ID: <1200247733-sup-3710@tomsk> (raw)
In-Reply-To: <1200201168-sup-5812@south>
On 13.1.2008, William Morgan wrote:
> 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.
I dont use it when I know the search will generate a lot of threads :)
What I'm working on is getting it to stop searching if the user
presses a key (so you get a progress of 'Found ??? threads (press ESC
to stop)' or something, but no luck yet :(
I guess it doesnt actually have to return the threads a la gmail
(gmail lets you select all threads in search without actually
displaying them but its _fast_). I tried doing this but since the
majority of searches I do end up being with labels I think you
actually need to thread them in order to be of any use (because not
all labels are on every message in thread).
I can resubmit once I figure out the interrupt.
Marcus
next prev parent reply other threads:[~2008-01-13 18:16 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
2008-01-13 15:57 ` Nicolas Pouillard
2008-01-13 18:16 ` Marcus Williams [this message]
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=1200247733-sup-3710@tomsk \
--to=marcus-sup@bar-coded.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