Re: [PATCH] v2 emacs: colorize buttonized 'id:' links depending on the target message...

diff --git a/d5/e5f90139cdb9754cd2351e7d0bfba27f7c662b b/d5/e5f90139cdb9754cd2351e7d0bfba27f7c662b
new file mode 100644 (file)
index 0000000..361b8ad
--- /dev/null
+++ b/d5/e5f90139cdb9754cd2351e7d0bfba27f7c662b
@@ -0,0 +1,101 @@
+Return-Path: <pieter@praet.org>\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 8A5FB429E54\r
+       for <notmuch@notmuchmail.org>; Sun, 22 Jan 2012 00:42:25 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 MG0Vfmlum+ej for <notmuch@notmuchmail.org>;\r
+       Sun, 22 Jan 2012 00:42:24 -0800 (PST)\r
+Received: from mail-we0-f181.google.com (mail-we0-f181.google.com\r
+       [74.125.82.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id AE2FD429E40\r
+       for <notmuch@notmuchmail.org>; Sun, 22 Jan 2012 00:42:24 -0800 (PST)\r
+Received: by werb10 with SMTP id b10so1653127wer.26\r
+       for <notmuch@notmuchmail.org>; Sun, 22 Jan 2012 00:42:23 -0800 (PST)\r
+Received: by 10.181.12.106 with SMTP id ep10mr5541049wid.8.1327221743477;\r
+       Sun, 22 Jan 2012 00:42:23 -0800 (PST)\r
+Received: from localhost ([109.131.95.182])\r
+       by mx.google.com with ESMTPS id ho4sm6735864wib.3.2012.01.22.00.42.21\r
+       (version=TLSv1/SSLv3 cipher=OTHER);\r
+       Sun, 22 Jan 2012 00:42:22 -0800 (PST)\r
+From: Pieter Praet <pieter@praet.org>\r
+To: Mark Anderson <MarkR.Anderson@amd.com>, Aaron Ecay <aaronecay@gmail.com>,\r
+       David Edmondson <dme@dme.org>,\r
+       Jameson Graef Rollins <jrollins@finestructure.net>\r
+Subject: Re: [PATCH] v2 emacs: colorize buttonized 'id:' links depending on\r
+       the target message's state\r
+In-Reply-To: <3wd39bambi6.fsf@testarossa.amd.com>\r
+References: <87hazva8qe.fsf@praet.org>\r
+       <1326733053-25185-1-git-send-email-pieter@praet.org>\r
+       <m2sjjfb9xx.fsf@gmail.com> <87aa5l8gqx.fsf@praet.org>\r
+       <3wd39bambi6.fsf@testarossa.amd.com>\r
+User-Agent: Notmuch/0.11+101~g94bf862 (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-unknown-linux-gnu)\r
+Date: Sun, 22 Jan 2012 09:40:30 +0100\r
+Message-ID: <871uqsku4h.fsf@praet.org>\r
+MIME-Version: 1.0\r
+X-Gm-Message-State:\r
+ ALoCoQkVpwGWMqPlt8FbzhYTZU2Q+lbYIflQm3EoTrvUY++gWDC9fTj96eVb0I74hnXfrYcwjSti\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+Cc: Notmuch Mail <notmuch@notmuchmail.org>\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, 22 Jan 2012 08:42:25 -0000\r
+\r
+On Fri, 20 Jan 2012 12:15:13 -0700, Mark Anderson <MarkR.Anderson@amd.com> =\r
+wrote:\r
+> On Wed, 18 Jan 2012 04:08:54 -0600, Pieter Praet <pieter@praet.org> wrote:\r
+> > On Mon, 16 Jan 2012 16:43:06 -0500, Aaron Ecay <aaronecay@gmail.com> wr=\r
+ote:\r
+> > > On Mon, 16 Jan 2012 17:57:33 +0100, Pieter Praet <pieter@praet.org> w=\r
+rote:\r
+> > > [...] Maybe you could change the regex that\r
+> > > matches id:=E2=80=99s to require a little more structure =E2=80=93 an=\r
+ at-sign, perhaps.\r
+> > > Or even requiring more than (say) 5 non-space characters after the\r
+> > > message id would cut down sharply on the false positive rate.\r
+> > >=20\r
+> >=20\r
+> > Not sure how that would pan out.  It's fairly common behaviour to put\r
+> > one or more spaces after a inline Message-Id, so I don't think such a\r
+> > limitation would be warmly recepted.\r
+>=20\r
+> I thought this was a suggestion to have more than 5 non-space characters\r
+> after the id:, not the full id:LongIdThingHere=20\r
+>=20\r
+\r
+Now that you mention it...\r
+\r
+I may have taken Aaron's suggestion a bit too literally. :)\r
+\r
+> It sounded to me like an attempt to prevent extra false positives and\r
+> the confusing buttonizing and notmuch queries that go with them.\r
+>=20\r
+> -Mark\r
+>=20\r
+\r
+\r
+Peace\r
+\r
+--=20\r
+Pieter\r