From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs426207agc; Sun, 1 Nov 2009 15:45:29 -0800 (PST) Received: by 10.224.96.71 with SMTP id g7mr2519415qan.77.1257119128718; Sun, 01 Nov 2009 15:45:28 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 32si6848994qyk.52.2009.11.01.15.45.28; Sun, 01 Nov 2009 15:45:28 -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 6B1D318582D3; Sun, 1 Nov 2009 18:45:28 -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 5709C18582C5 for ; Sun, 1 Nov 2009 18:42:39 -0500 (EST) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1N4k4E-0005Kq-Qu for sup-talk@rubyforge.org; Sun, 01 Nov 2009 18:42:38 -0500 From: Rich Lane To: sup-talk Date: Sun, 01 Nov 2009 18:42:38 -0500 Message-Id: <1257118189-sup-7392@zyrg.net> User-Agent: Sup/git Subject: [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 I've pushed a few more commits to http://github.com/rlane/sup/tree/experimental The major feature on this branch is the immediate label updates I've mentioned before on the list. The bulk of the actual changes are basically consequences of this feature: Use of Xapian for thread relevance checks - Instead of hardcoding the policy into InboxMode - 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 - Saves us from (half of the) adding/removing threads changes cursor_thread problem - Relevant messages added to thread-index-modes without reload Async message state saving - Keeps the UI responsive - Prepares us for a sup-server future Fallout from async message saving - UpdateManager messages handled in main event loop - Avoids many races but can lag UI unless we're careful New, simpler undo implementation - Still needs work at a few use-sites to be completely correct Let me know what you all think of these changes. I'll need to do a lot of rebasing before this branch is clean enough to be merged. A couple of bugs I know about: - Discarding drafts is disabled - Occasionally, new messages in an existing undisplayed thread fail to get added to the ThreadSet. I haven't been able to come up with a test case for this, so if someone wants to give that a shot it would be very helpful. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk