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. > What just happened to me is that I *knew* my inbox contained a message > with a particular string in the subject, but I couldn't find it with > '/'. The problem was that enough new threads had arrived that the > message of interest wasn't loaded yet. If you know it's in your inbox, why not search with '\', for 'label:inbox foo'? > The fact that the various ThreadIndexModes don't load all relevant > threads is just an optimization, but I don't think it should change > the semantics of a search operation. (My thread *is* still in my inbox > even if it hasn't been loaded.) > > Of course, for the feature I want to work well there needs to be an > easy way to interrupt the searching and loading if it's going on too > long, (say, I mistyped the search string and I know it's likely to > load a million messages without ever finding the string I typed). > > Does sup already have a notion like emacs' "C-g" which is used to > cancel or interrupt any ongoing command? Try C-g. :-) (Documented as ^G on the help page) > -Carl -- Exherbo KDE, X.org maintainer _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
