Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 981F1429E54 for ; Sun, 22 Jan 2012 09:31:50 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diTkA-XCLZ7Z for ; Sun, 22 Jan 2012 09:31:50 -0800 (PST) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by olra.theworths.org (Postfix) with ESMTP id 1C0F8429E40 for ; Sun, 22 Jan 2012 09:31:50 -0800 (PST) X-AuditID: 1209190f-b7f8a6d000000914-29-4f1c480569e8 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id A6.37.02324.5084C1F4; Sun, 22 Jan 2012 12:31:49 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id q0MHVnnK020140; Sun, 22 Jan 2012 12:31:49 -0500 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q0MHVmoW021878 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sun, 22 Jan 2012 12:31:48 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1Rp1GD-0001js-W9; Sun, 22 Jan 2012 12:31:22 -0500 Date: Sun, 22 Jan 2012 12:31:21 -0500 From: Austin Clements To: Mark Walters Subject: Re: [PATCH] Automatically exclude tags in notmuch-show Message-ID: <20120122173121.GP16740@mit.edu> References: <874nvric7c.fsf@qmul.ac.uk> <1327010583-23954-1-git-send-email-markwalters1009@gmail.com> <20120119225910.GT16740@mit.edu> <871uqvgrnm.fsf@qmul.ac.uk> <20120120171801.GA16740@mit.edu> <87sjj8efkv.fsf@qmul.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87sjj8efkv.fsf@qmul.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphleLIzCtJLcpLzFFi42IRYrdT12X1kPE3uL5UyGL1XB6L6zdnMjsw eeycdZfd49mqW8wBTFFcNimpOZllqUX6dglcGUdf/GQqeMRZMeH2KsYGxofsXYycHBICJhKH 929ghbDFJC7cW8/WxcjFISSwj1Hi1KnF7BDOBkaJq/NXs0I4J5kk5k9bwQjhLGGUWDWjjwWk n0VAVeLr5N+MIDabgIbEtv3LwWwRAR2J24cWgO1jFpCW+Pa7mQnEFhawl5i8dDEziM0LVDPp 6lWooS8ZJbq657JCJAQlTs58wgLRrCVx499LoGYOsEHL/3GAhDmBdn38dw+sXFRARWLKyW1s ExiFZiHpnoWkexZC9wJG5lWMsim5Vbq5iZk5xanJusXJiXl5qUW6Jnq5mSV6qSmlmxhBgc0p yb+D8dtBpUOMAhyMSjy8WbIy/kKsiWXFlbmHGCU5mJREeZucgUJ8SfkplRmJxRnxRaU5qcWH GCU4mJVEeJ0/S/sL8aYkVlalFuXDpKQ5WJTEedW03vkJCaQnlqRmp6YWpBbBZGU4OJQkeKe7 Aw0VLEpNT61Iy8wpQUgzcXCCDOcBGt4NUsNbXJCYW5yZDpE/xagoJc5bApIQAElklObB9cIS zytGcaBXhHnTQKp4gEkLrvsV0GAmoMEceVIgg0sSEVJSDYxCUxPWB+x2yRP1N3FRjFJ7ctBR RfaabGrfQ7EH/Ds7Nj5hKIouiF+/3TLsbtjS3x1MQpWX95Vl53cb6aoo2Od8Wn1527NFCl/O XBKbqFbRys76/bPxpL2NSse2rnpgENd0lPeryTLmF2VZF3MZdvRzVnv3nbzD/eih9ZYf0rPr 3XbF5cp9rlViKc5INNRiLipOBACK958sFwMAAA== Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2012 17:31:50 -0000 Quoth Mark Walters on Jan 22 at 12:38 am: > > On Fri, 20 Jan 2012 12:18:01 -0500, Austin Clements wrote: > > > > Oh dear. > > > > Well, here's one idea. Instead of doing a single thread query in > > show, do a thread query without the exclusions and then a message > > query with the exclusions. Output all of the messages from the first > > query, but use the results of the second query to determine which > > messages are "matched". The same could be accomplished in the library > > somewhat more efficiently, but it's not obvious to me what the API > > would be. > > I have been thinking about this and one question is what should the sort > order be? If I understand it correctly notmuch sorts the threads > by the oldest/newest matching message, so the "correct" behaviour if no > message matches is unclear. Perhaps all threads with a matching > non-excluded message sorted by the matching-non-excluded message > followed by all threads that match only on excluded messages with sort > based on the matching excluded message? I don't think show sorts in any particular way. Or are you saying that search also needs to know the difference between excluded and non-excluded matched messages?