1 Return-Path: <daniel@schoepe.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 1FD95429E27
\r
6 for <notmuch@notmuchmail.org>; Mon, 17 Oct 2011 05:13:17 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.512 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
\r
13 FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_LOW=-0.7,
\r
14 T_MIME_NO_TEXT=0.01] autolearn=disabled
\r
15 Received: from olra.theworths.org ([127.0.0.1])
\r
16 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
17 with ESMTP id 6I6HX8V36FEg for <notmuch@notmuchmail.org>;
\r
18 Mon, 17 Oct 2011 05:13:16 -0700 (PDT)
\r
19 Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com
\r
20 [209.85.213.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
21 (No client certificate requested)
\r
22 by olra.theworths.org (Postfix) with ESMTPS id 5E3D3429E25
\r
23 for <notmuch@notmuchmail.org>; Mon, 17 Oct 2011 05:13:16 -0700 (PDT)
\r
24 Received: by ywm19 with SMTP id 19so3013778ywm.26
\r
25 for <notmuch@notmuchmail.org>; Mon, 17 Oct 2011 05:13:16 -0700 (PDT)
\r
26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=schoepe.org; s=google;
\r
27 h=sender:from:to:cc:subject:in-reply-to:references:user-agent:date
\r
28 :message-id:mime-version:content-type;
\r
29 bh=knpbVWxea7Ks1LVbi5z3PeYcRbkjNC3mKj4SHmS9PXQ=;
\r
30 b=Qq+h8s2asmT7fqJmUKKkFbPse/orunXCY4lBjnniH2VcJmFAXN3PhmLGq+8dh7/S+q
\r
31 JlgHQSCVr8DfYJojot2xLfZKD9vVVzmTXrmM4yB0+Fsc8wWCNW3RCOwx81DDbEjMXeI+
\r
32 UuaN2GsOzz7TROoVsZTSiblpLyyJBDsu7ipB0=
\r
33 Received: by 10.223.5.3 with SMTP id 3mr23953503fat.4.1318853595649;
\r
34 Mon, 17 Oct 2011 05:13:15 -0700 (PDT)
\r
35 Received: from localhost (s0200.dyn.hrz.tu-darmstadt.de. [130.83.104.200])
\r
36 by mx.google.com with ESMTPS id u6sm23282585fan.17.2011.10.17.05.13.13
\r
37 (version=TLSv1/SSLv3 cipher=OTHER);
\r
38 Mon, 17 Oct 2011 05:13:14 -0700 (PDT)
\r
39 Sender: Daniel Schoepe <daniel@schoepe.org>
\r
40 From: Daniel Schoepe <daniel.schoepe@googlemail.com>
\r
41 To: Thomas Schwinge <thomas@schwinge.name>
\r
42 Subject: Re: [PATCH v2] emacs: Turn id:"<message-id>" elements into buttons
\r
43 for notmuch searches
\r
44 In-Reply-To: <8739es0ygy.fsf@kepler.schwinge.homeip.net>
\r
45 References: <1309896760-378-1-git-send-email-daniel.schoepe@googlemail.com>
\r
46 <1309961881-28333-1-git-send-email-daniel.schoepe@googlemail.com>
\r
47 <1309961881-28333-2-git-send-email-daniel.schoepe@googlemail.com>
\r
48 <8739es0ygy.fsf@kepler.schwinge.homeip.net>
\r
49 User-Agent: Notmuch/0.9-19-g4753484 (http://notmuchmail.org) Emacs/23.3.1
\r
51 Date: Mon, 17 Oct 2011 14:13:05 +0200
\r
52 Message-ID: <87hb37n7e6.fsf@tredergarh.home.box>
\r
54 Content-Type: multipart/signed; boundary="=-=-=";
\r
55 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
56 Cc: notmuch@notmuchmail.org
\r
57 X-BeenThere: notmuch@notmuchmail.org
\r
58 X-Mailman-Version: 2.1.13
\r
60 List-Id: "Use and development of the notmuch mail system."
\r
61 <notmuch.notmuchmail.org>
\r
62 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
64 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
65 List-Post: <mailto:notmuch@notmuchmail.org>
\r
66 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
67 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
68 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
69 X-List-Received-Date: Mon, 17 Oct 2011 12:13:17 -0000
\r
72 Content-Transfer-Encoding: quoted-printable
\r
74 On Mon, 17 Oct 2011 11:16:45 +0200, Thomas Schwinge <thomas@schwinge.name> =
\r
76 > Is it permissible for message IDs to contain double quotes? If not (and
\r
77 > I hope so), might id:\"[^\"]+\" be a better regexp? (Untested.) As it
\r
78 > appears to me, this would allow proper matching in text like this, too:
\r
80 > Bla bla, see id:"some@thing". Bla bla.
\r
82 My patch already works for this example, and I don't think spaces are
\r
83 allowed in message IDs, so it shouldn't make a difference.
\r
85 > Even if not favorable, should a syntax without double quotes be
\r
86 > supported, too? Here we'd really have to match on whitespace and line
\r
87 > end, as everything else is too ambiguous.
\r
89 I guess the syntaxes we have to support are those produced by notmuch
\r
90 frontends, at least until other mailing lists start using this kind of
\r
91 references as well. I don't think the quotes are necessary, since the
\r
92 IDs don't contain any spaces, so your suggestion would be
\r
93 preferable (of course, that might lead to more id:..-texts turned into
\r
94 links even though they aren't intended to be).=20
\r
95 I'll send an edited patch later.
\r
101 Content-Type: application/pgp-signature
\r
103 -----BEGIN PGP SIGNATURE-----
\r
104 Version: GnuPG v1.4.11 (GNU/Linux)
\r
106 iQIcBAEBAgAGBQJOnBvRAAoJEIaTAtce+Z+J/F0P/jOH/MEQ+cZRk4l8mPvs1ruL
\r
107 erIHFnW0jXBb16ScpHbKOJgEBqv7s8NdIR558/ovrPW44Q1LPvvVb+zyAY2pjUUq
\r
108 1/CHDnceyG/6ki0JHoP9ZbUYk9c1nzuZDhZyr7A+mVnD+Gsc4Xtjnz7BYpJIZ9SM
\r
109 XB5YrcUxE6mWTNyD+lTM5agRvfimqhOlXFPPNp4aQiUA9s/fXB9ofk+HlYkeqeP/
\r
110 L0V9z5UxPGiknvYpDJN7VTGCjLgaoON0f8qWZPFEwo8tUMygM5vNHqnF/Hd2SqqZ
\r
111 O6isW4OX9otbqxFhBz5j8xf4dA/STtK8eunIu2loWjiPiZ5OE3V8Ie1k6I675kgV
\r
112 wK5Fvg93sH17q7h+vGW6PD78Ot2Us05dib6DAVFAaAPk3LwJSa8HKmsiFgRGUCaU
\r
113 6uf/k0v+4YPsOrEwkTEoA24pkjTfZES1nFjYiB8f+11qhOSqI3t3KDRxaPToeeEe
\r
114 ZHeB/amAazDizblib3jOXPe80M33nOAHSZQ0/VAafORnI9so1E6vOgMqAuVfaGJ/
\r
115 4fI0teWpkYehHrzSb+hHFAkXSoVEbuXu0LBCfvdXrhwdWpLeVlN7DllWu7KA9USj
\r
116 nkG3iW0DlVkFNmQr730ecperHKyKQxLwxjUtDtOxWQKrZkRQMuF5/Z8TKbI030W/
\r
117 k3QfBaISNlDjDLoo38Em
\r
119 -----END PGP SIGNATURE-----
\r