Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] On making inbox-mode and search-results-mode more similar
Date: Thu, 03 Sep 2009 14:44:06 -0400	[thread overview]
Message-ID: <1252003316-sup-2379@zyrg.net> (raw)
In-Reply-To: <1252002783-sup-3659@masanjin.net>

Excerpts from William Morgan's message of Thu Sep 03 14:36:42 -0400 2009:
> Reformatted excerpts from Rich Lane's message of 2009-08-26:
> > We had a thread a while back about applying label changes immediately
> > and I think the consensus was that that's a good idea. Doing this
> > could simplify a great deal of thread-index-mode code because a fast
> > is_relevant? could be implemented using existing index operations
> > without the special cases for archiving/etc and without creating an
> > inmemory database.
> 
> But it's not just a label issue. Determining whether a given message
> belongs in a general search buffer requires the full engine. And even if
> the query is just on labels, it can contain arbitrary boolean
> expressions, and I don't want to be the one having to parse that, and
> parse it in such a way that it matches what the search engine is doing.

You're right that it require the full engine. If we're immediately
saving the label changes to the (on-disk) index, we can simply query it
and get the correct answer.


  reply	other threads:[~2009-09-03 18:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 22:24 Carl Worth
2009-08-26 22:52 ` Carl Worth
2009-09-03 18:39   ` William Morgan
2009-08-27  6:50 ` Rich Lane
2009-09-03 18:36   ` William Morgan
2009-09-03 18:44     ` Rich Lane [this message]
2009-09-03 18:50       ` William Morgan
2009-09-03 18:32 ` William Morgan
2009-10-06 17:30 ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1252003316-sup-2379@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox