Reformatted excerpts from Carl Worth's message of 2009-08-26: > So what I want is for anytime a message is changed such that it no > longer meets the current search criteria, it is immediately removed > from the search results. I think that means simply implementing the > is_relevant? method for SearcResultsMode
is_relevant? is currently only used for determining when to add messages to a thread-index-mode (e.g. when a new message is picked up during a poll). Determining whether to drop a message is currently done "manually" by inbox-mode, and not at all by search-results-mode. > That single-message index and search sounds exactly like what I want, > and not insane at all. Hm. Well, you could certainly try it. I've assumed it would be too slow, but it's possible it'd be fast enough. I think it's the only option though, if you want this to work with arbitrary queries. > (In which case, I'll try, and I'll be glad for any pointers that > anyone can give me on how to go about creating an in-memory index and > searching on it.) Excellent, ask Rich. :) > The command I would find natural for putting a thread back into the > inbox would be to simply add the inbox label to the thread. Oddly this > is currently not allowed as "inbox" is a reserved label. Yeah, there's no good reason for this. I was just being overly protective. :) -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
