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.
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. 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? -Carl
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
