Excerpts from Ingmar Vanhassel's message of Wed Aug 26 19:37:57 -0700 2009: > Excerpts from Carl Worth's message of Thu Aug 27 00:47:54 +0200 2009: > > It seems to me that the "search in current buffer" command should > > automatically trigger the loading of additional messages when no > > results are found so that it can continue searching. > > I'd expect a "search in current buffer" to do exactly that, no more no > less.
You obviously know well what the current buffer is doing, (incrementally loading threads only as you page down to them). But I don't think it's reasonable to expect all users to understand things that well in order to use sup correctly. Imagine the near future where we get the thread-loading performance bugs all worked out, (see nearby threads making good progress). If a user starts sup and sees a screenful of threads instantly, hits page down a couple of times and sees another couple of screensful instantly, then wouldn't it be reasonable for such a user to expect that all of that instantly-appearing content does exist in the current buffer? > If you know it's in your inbox, why not search with '\', for > 'label:inbox foo'? I'm searching locally, because I already performed a global search and don't want to repeat the terms of it. Or else why does sup have a local search command independent of the global search? > Try C-g. :-) > (Documented as ^G on the help page) Ah, thanks. Now this one was just me being stupid. (I think I was already using this in sup naturally.) -Carl
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
