Re: [PATCH 3/5] nmbug-status: Add an nmbug-status(5) man page
[notmuch-archives.git] / 16 / b106464a40f83871a7649def1825c12e511bde
1 Return-Path: <aaronecay@gmail.com>\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 A6272431FB6\r
6         for <notmuch@notmuchmail.org>; Thu, 19 Jan 2012 14:56:19 -0800 (PST)\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -0.799\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
12         tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
13         FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
14 Received: from olra.theworths.org ([127.0.0.1])\r
15         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
16         with ESMTP id nSLMyQaSLyMc for <notmuch@notmuchmail.org>;\r
17         Thu, 19 Jan 2012 14:56:19 -0800 (PST)\r
18 Received: from mail-qw0-f53.google.com (mail-qw0-f53.google.com\r
19         [209.85.216.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
20         (No client certificate requested)\r
21         by olra.theworths.org (Postfix) with ESMTPS id 410A3431FAF\r
22         for <notmuch@notmuchmail.org>; Thu, 19 Jan 2012 14:56:19 -0800 (PST)\r
23 Received: by qabg24 with SMTP id g24so430855qab.5\r
24         for <notmuch@notmuchmail.org>; Thu, 19 Jan 2012 14:56:18 -0800 (PST)\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;\r
26         h=from:to:cc:subject:in-reply-to:references:user-agent:date\r
27         :message-id:mime-version:content-type:content-transfer-encoding;\r
28         bh=SxNp9PUvkiUfqAgkR9nZuwdS/Eu9djOh/UyNJrWGzFM=;\r
29         b=uEL3NBHj1yjCqQy6k2l/7Z6G95ztKcjAYXyCGVOL/tdfOt3WkmkWFCKU9qVge8ID4E\r
30         BiIIokUdifzu03bsr96kyGyFZz81AxBEEzBupkh54GEMapZ6bGgXpj98GyX82lZw14MK\r
31         OmDdfJutaUkiJYr4fQq3tH8bqYpTdUsEMu4Bo=\r
32 Received: by 10.224.192.10 with SMTP id do10mr29947600qab.50.1327013778745;\r
33         Thu, 19 Jan 2012 14:56:18 -0800 (PST)\r
34 Received: from localhost (wal016.wlan.sas.upenn.edu. [128.91.71.145])\r
35         by mx.google.com with ESMTPS id ft9sm2389479qab.20.2012.01.19.14.56.17\r
36         (version=TLSv1/SSLv3 cipher=OTHER);\r
37         Thu, 19 Jan 2012 14:56:17 -0800 (PST)\r
38 From: Aaron Ecay <aaronecay@gmail.com>\r
39 To: Austin Clements <amdragon@MIT.EDU>\r
40 Subject: Re: [PATCH] emacs: Quote MML tags in replies\r
41 In-Reply-To: <20120119224842.GS16740@mit.edu>\r
42 References: <1326998589-37187-1-git-send-email-aaronecay@gmail.com>\r
43         <20120119224842.GS16740@mit.edu>\r
44 User-Agent: Notmuch/0.11+73~gd51b784 (http://notmuchmail.org) Emacs/24.0.92.2\r
45         (i386-apple-darwin10.8.0)\r
46 Date: Thu, 19 Jan 2012 17:56:16 -0500\r
47 Message-ID: <m2vco72tf3.fsf@wal122.wireless-pennnet.upenn.edu>\r
48 MIME-Version: 1.0\r
49 Content-Type: text/plain; charset=utf-8\r
50 Content-Transfer-Encoding: quoted-printable\r
51 Cc: notmuch@notmuchmail.org\r
52 X-BeenThere: notmuch@notmuchmail.org\r
53 X-Mailman-Version: 2.1.13\r
54 Precedence: list\r
55 List-Id: "Use and development of the notmuch mail system."\r
56         <notmuch.notmuchmail.org>\r
57 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
58         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
59 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
60 List-Post: <mailto:notmuch@notmuchmail.org>\r
61 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
62 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
63         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
64 X-List-Received-Date: Thu, 19 Jan 2012 22:56:19 -0000\r
65 \r
66 On Thu, 19 Jan 2012 17:48:42 -0500, Austin Clements <amdragon@MIT.EDU> wrot=\r
67 e:\r
68 > Did you consider using point-max instead of mark?  IIRC, that mark was\r
69 > very recently introduced which, perhaps irrationally, makes it seem\r
70 > less future-proof to me.\r
71 \r
72 Well, if the patch goes in and someone changes the code so that it no\r
73 longer sets the mark (in the same way), they will be the one breaking\r
74 stuff, and they=E2=80=99ll have to come up with the fix themself.  Using po=\r
75 int-max\r
76 would include the signature in the quoting as well.  It would probably be\r
77 fairly odd to want to put an MML tag in one=E2=80=99s signature, but that d=\r
78 oesn=E2=80=99t\r
79 mean that we should break that usage.\r
80 \r
81 >=20\r
82 > >=20=20\r
83 > >  (defun notmuch-mua-forward-message ()\r
84 > >    (message-forward)\r
85 >=20\r
86 > Speaking of future-proofing, it would be good to have a test.\r
87 \r
88 It would.  ;)  I=E2=80=99ll work on one.\r
89 \r
90 --=20\r
91 Aaron Ecay\r