Re: Header and other questions

diff --git a/99/73088f7db82ae970dc93f9fec0497663b7763d b/99/73088f7db82ae970dc93f9fec0497663b7763d
new file mode 100644 (file)
index 0000000..94c4cc1
--- /dev/null
+++ b/99/73088f7db82ae970dc93f9fec0497663b7763d
@@ -0,0 +1,81 @@
+Return-Path: <prvs=1105b71d9=jrosenthal@jhu.edu>\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 2829C431FD0\r
+       for <notmuch@notmuchmail.org>; Mon, 16 May 2011 08:27:56 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] 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 eRHl5jNuP62A for <notmuch@notmuchmail.org>;\r
+       Mon, 16 May 2011 08:27:54 -0700 (PDT)\r
+Received: from ipex4.johnshopkins.edu (ipex4.johnshopkins.edu\r
+       [128.220.161.141]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id E6647431FB6\r
+       for <notmuch@notmuchmail.org>; Mon, 16 May 2011 08:27:53 -0700 (PDT)\r
+X-IronPort-AV: E=Sophos;i="4.64,374,1301889600"; d="scan'208";a="70265007"\r
+Received: from dyn-butler-159-101.dyn.columbia.edu (HELO gogo.home)\r
+       ([128.59.159.101])\r
+       by ipex4.johnshopkins.edu with ESMTP/TLS/AES256-SHA;\r
+       16 May 2011 11:27:52 -0400\r
+Received: from jkr by gogo.home with local (Exim 4.75)\r
+       (envelope-from <jrosenthal@jhu.edu>)\r
+       id 1QLzi4-0004LH-9P; Mon, 16 May 2011 11:27:52 -0400\r
+From: Jesse Rosenthal <jrosenthal@jhu.edu>\r
+To: Daniel Schoepe <daniel.schoepe@googlemail.com>,\r
+       Xavier Maillard <xma@gnu.org>, mueen@nawaz.org, notmuch@notmuchmail.org\r
+Subject: Re: Header and other questions\r
+In-Reply-To: <87vcxad6d6.fsf@gilead.home.box>\r
+References: <878vu8edvf.fsf@fester.com> <m2sjsfmxvo.fsf@gnu.org>\r
+       <87hb8vwqww.fsf@lucky.home> <87vcxad6d6.fsf@gilead.home.box>\r
+User-Agent: Notmuch/0.5-192-gecd6549 (http://notmuchmail.org) Emacs/23.3.1\r
+       (i486-pc-linux-gnu)\r
+Date: Mon, 16 May 2011 11:27:52 -0400\r
+Message-ID: <874o4uy8av.fsf@gogo.home>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\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: Mon, 16 May 2011 15:27:56 -0000\r
+\r
+\r
+Hi,\r
+\r
+On Mon, 16 May 2011 17:15:17 +0200, Daniel Schoepe <daniel.schoepe@googlemail.com> wrote:\r
+> I think this is only a subset of the requested functionality, since one\r
+> can only tag consecutive threads at once.\r
+\r
+It seems like for non-consecutive messages to be tagged, there'd have to\r
+be some sort of mutt-style message-marking facility. There was some\r
+discussion when the feature was first introduced about whether to go\r
+with region or marking. I think I wrote a quick version of both. (I just\r
+checked -- that uncertainty is actually still there in the commit msg of\r
+4c9585933 where the region feature comes in.)\r
+\r
+The decision, if I remember correctly, was that regions are so intuitive\r
+for emacs users, and many people reported trying to tag by region\r
+without thinking about it, that this approach would make sense for the\r
+emacs interface. In other words, keep the emacs interface emacsy. I\r
+think I still agree with that, since I feel like having both would be\r
+confusing (what do you do when you select a marked-line in a region?)\r
+and I like the one I tend toward intuitively. But I certainly see the\r
+benefit of the other functionality as well.\r
+\r
+Best,\r
+Jesse\r