From mboxrd@z Thu Jan  1 00:00:00 1970
From: marcus-sup@bar-coded.net (Marcus Williams)
Date: Sun, 13 Jan 2008 18:16:12 +0000
Subject: [sup-talk] [PATCH] (Double/guarded) keypress to show all threads
In-Reply-To: <1200201168-sup-5812@south>
References: <1200071751-sup-5552@tomsk> <1200201168-sup-5812@south>
Message-ID: <1200247733-sup-3710@tomsk>

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