Re: [sup-talk] updated xapian experimental branch

From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] updated xapian experimental branch
Date: Mon, 02 Nov 2009 22:48:10 -0500	[thread overview]
Message-ID: <1257196293-sup-6882@zyrg.net> (raw)
In-Reply-To: <1257163403-sup-9032@masanjin.net>

Excerpts from William Morgan's message of Mon Nov 02 07:08:09 -0500 2009:
> >  - New 'z' key to clear irrelevant threads
> >   - Not strictly necessary, but removing messages in response to index
> >     events is difficult with the current UI code
> 
> Can you describe this a bit?

In general, we can only determine thread relevance by querying xapian.
The actual write to the db is done async, so it will happen a little
after you (for example) remove a label. The index fires a message event
when the new state hits the db, and the UI then checks if the thread is
still relevant to the query. So, the UI would only know to hide a newly
irrelevant thread after the user has potentially gone on and done other
actions. Having threads randomly disappear would be unfriendly, so
instead the UI displays a red X. 'z' will drop these irrelevant threads.

For 'simple' queries we can determine relevance without xapian, so we
could synchronously remove irrelevant threads in that case. However,
this would lead to unintuitive situations where queries that appear
similar have different irrelevance behaviors. The option that I will
probably implement is choosing the behavior per-mode, so that inbox-mode
could keep it's old behavior. That's the most important one anyway.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk