From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs20492agb; Mon, 2 Nov 2009 19:48:16 -0800 (PST) Received: by 10.224.79.22 with SMTP id n22mr3337402qak.230.1257220095648; Mon, 02 Nov 2009 19:48:15 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 32si8182903qyk.52.2009.11.02.19.48.15; Mon, 02 Nov 2009 19:48:15 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 59747159807F; Mon, 2 Nov 2009 22:48:15 -0500 (EST) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id 82C221588065 for ; Mon, 2 Nov 2009 22:48:10 -0500 (EST) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1N5ANO-0007a0-AU for sup-talk@rubyforge.org; Mon, 02 Nov 2009 22:48:10 -0500 From: Rich Lane To: sup-talk In-reply-to: <1257163403-sup-9032@masanjin.net> References: <1257118189-sup-7392@zyrg.net> <1257163403-sup-9032@masanjin.net> Date: Mon, 02 Nov 2009 22:48:10 -0500 Message-Id: <1257196293-sup-6882@zyrg.net> User-Agent: Sup/git Subject: Re: [sup-talk] updated xapian experimental branch X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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