Re: [PATCH v5 00/12] emacs: more flexible and consistent tagging operations
authorDavid Bremner <david@tethera.net>
Sat, 25 Feb 2012 16:20:31 +0000 (12:20 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:44:58 +0000 (09:44 -0800)
5c/1d21cf455ba19997d31c0a65b7ad9254f1dba0 [new file with mode: 0644]

diff --git a/5c/1d21cf455ba19997d31c0a65b7ad9254f1dba0 b/5c/1d21cf455ba19997d31c0a65b7ad9254f1dba0
new file mode 100644 (file)
index 0000000..7898cb1
--- /dev/null
@@ -0,0 +1,75 @@
+Return-Path: <bremner@unb.ca>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id B2FED431FC2\r
+       for <notmuch@notmuchmail.org>; Sat, 25 Feb 2012 22:02:59 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id CIBhWayduTus for <notmuch@notmuchmail.org>;\r
+       Sat, 25 Feb 2012 22:02:57 -0800 (PST)\r
+Received: from tesseract.cs.unb.ca (tesseract.cs.unb.ca [131.202.240.238])\r
+       (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 95A0E431FD8\r
+       for <notmuch@notmuchmail.org>; Sat, 25 Feb 2012 22:02:49 -0800 (PST)\r
+Received: from fctnnbsc30w-142166230117.dhcp-dynamic.fibreop.nb.bellaliant.net\r
+       ([142.166.230.117] helo=zancas.localnet)\r
+       by tesseract.cs.unb.ca with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32)\r
+       (Exim 4.72) (envelope-from <bremner@unb.ca>)\r
+       id 1S1KMQ-0001tu-0a; Sat, 25 Feb 2012 12:20:38 -0400\r
+Received: from bremner by zancas.localnet with local (Exim 4.77)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1S1KMJ-0007s3-Sg; Sat, 25 Feb 2012 12:20:31 -0400\r
+From: David Bremner <david@tethera.net>\r
+To: Pieter Praet <pieter@praet.org>,\r
+       Dmitry Kurochkin <dmitry.kurochkin@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH v5 00/12] emacs: more flexible and consistent tagging\r
+       operations\r
+In-Reply-To: <878vjtqhcg.fsf@praet.org>\r
+References: <1327725684-5887-1-git-send-email-dmitry.kurochkin@gmail.com>\r
+       <1328426033-21480-1-git-send-email-dmitry.kurochkin@gmail.com>\r
+       <87wr7xqpuf.fsf@rocinante.cs.unb.ca> <878vjtqhcg.fsf@praet.org>\r
+User-Agent: Notmuch/0.11.1+239~g4d2d96b (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sat, 25 Feb 2012 12:20:31 -0400\r
+Message-ID: <87haye6g1c.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Spam_bar: -\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 26 Feb 2012 06:03:00 -0000\r
+\r
+On Fri, 24 Feb 2012 00:07:27 +0100, Pieter Praet <pieter@praet.org> wrote:\r
+> On Wed, 08 Feb 2012 11:58:32 -0400, David Bremner <david@tethera.net> wrote:\r
+> > On Sun,  5 Feb 2012 11:13:41 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:\r
+> \r
+> How about if '*' applies to all messages (as it currently does),\r
+> but 'C-u *' only to open messages?  That would make more sense IMHO.\r
+> \r
+> But, conforming to your original request, I've implemented the inverse.\r
+> \r
+\r
+Thanks for implementing that. I could live with either way. Do other\r
+people have opinions on this? My reasoning is if you descend into a\r
+thread from some search page, it seems likely that you want to operate\r
+on the messages matching the search.\r
+\r
+d\r