From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs6439agb; Tue, 3 Nov 2009 00:53:58 -0800 (PST) Received: by 10.224.108.5 with SMTP id d5mr3471756qap.294.1257238437530; Tue, 03 Nov 2009 00:53:57 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 33si9955664qyk.128.2009.11.03.00.53.57; Tue, 03 Nov 2009 00:53:57 -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 D6764159807C; Tue, 3 Nov 2009 03:53:56 -0500 (EST) Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by rubyforge.org (Postfix) with ESMTP id 700ED18582C1 for ; Tue, 3 Nov 2009 03:39:49 -0500 (EST) X-IronPort-AV: E=Sophos;i="4.44,673,1249250400"; d="scan'208";a="39417791" Received: from peray.inria.fr (HELO localhost) ([128.93.8.98]) by mail1-relais-roc.national.inria.fr with ESMTP; 03 Nov 2009 09:39:48 +0100 From: Nicolas Pouillard To: Rich Lane In-reply-to: <1257196293-sup-6882@zyrg.net> References: <1257118189-sup-7392@zyrg.net> <1257163403-sup-9032@masanjin.net> <1257196293-sup-6882@zyrg.net> Date: Tue, 03 Nov 2009 09:39:48 +0100 Message-Id: <1257237468-sup-5663@peray> User-Agent: Sup/git Cc: sup-talk 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 Rich Lane's message of Tue Nov 03 04:48:10 +0100 2009: > 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. What are non simple queries which would cause 'red X's to appear? My guess is that since we cannot change other attributes than the labels, we can statically know if the thread is still relevant without the label. No? -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk