Re: [PATCH] emacs: wash: make word-wrap bound message width
[notmuch-archives.git] / 70 / 1196138797ef98a6b953c2605f5eca59dedb48
1 Return-Path: <novalazy@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 30553431FAF\r
6         for <notmuch@notmuchmail.org>; Tue,  3 Jul 2012 19:00:01 -0700 (PDT)\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 z9YbuXoMZAoX for <notmuch@notmuchmail.org>;\r
17         Tue,  3 Jul 2012 18:59:59 -0700 (PDT)\r
18 Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com\r
19         [209.85.160.181]) (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 22E6D431FAE\r
22         for <notmuch@notmuchmail.org>; Tue,  3 Jul 2012 18:59:59 -0700 (PDT)\r
23 Received: by ghbz13 with SMTP id z13so7825188ghb.26\r
24         for <notmuch@notmuchmail.org>; Tue, 03 Jul 2012 18:59:57 -0700 (PDT)\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
26         h=date:message-id:from:to:cc:subject:in-reply-to:references\r
27         :mime-version:content-type:content-disposition\r
28         :content-transfer-encoding;\r
29         bh=sQPt2vi55FlsamtfihEH1v7Tl2NPoZJlZcpCIWK8drg=;\r
30         b=eOcGgeo6TUDiTQ8IKStmjxcDe4KTFU7LY9RCRTyxam2VxMQhYk6VG0q3HuZgP/OfXC\r
31         xeFKDMWEeito0w/8cMWSMuqiqLxe4J7h2Yn+TNJedx3TgmK4yJ0sgqcKelv8amHgul54\r
32         /v+QoyGjxJvg/NGAL2EJWmjsGMK5IZ9u9HyiPISfTea9l0HkUCp5z3LLskTgvl2IdTOV\r
33         BSB22B64cfxsKxwE4nKfHFD2VuRxP7QKVLzRReYoiAbIQchd+sOmUMssYvc4/wFwViR9\r
34         jE1i8eboP23+X8OZDIRL2FMk53URVWAdtu0A+rhTty9m36KHcPRzAhATJEcpcL86tIkb\r
35         f1LA==\r
36 Received: by 10.68.194.201 with SMTP id hy9mr4165191pbc.69.1341367197232;\r
37         Tue, 03 Jul 2012 18:59:57 -0700 (PDT)\r
38 Received: from localhost (215.42.233.220.static.exetel.com.au.\r
39         [220.233.42.215])\r
40         by mx.google.com with ESMTPS id of1sm16662864pbb.15.2012.07.03.18.59.54\r
41         (version=TLSv1/SSLv3 cipher=OTHER);\r
42         Tue, 03 Jul 2012 18:59:56 -0700 (PDT)\r
43 Date: Wed, 4 Jul 2012 11:59:51 +1000\r
44 Message-ID: <20120704115951.GC2342@hili.localdomain>\r
45 From: Peter Wang <novalazy@gmail.com>\r
46 To: Jameson Graef Rollins <jrollins@finestructure.net>\r
47 Subject: Re: [PATCH 2/3] show: output Reply-To headers\r
48 In-Reply-To: <87vci471tw.fsf@servo.finestructure.net>\r
49 References: <1340508470-16606-1-git-send-email-novalazy@gmail.com>\r
50         <1340508470-16606-2-git-send-email-novalazy@gmail.com>\r
51         <87vci471tw.fsf@servo.finestructure.net>\r
52 MIME-Version: 1.0\r
53 Content-Type: text/plain; charset=utf-8\r
54 Content-Disposition: inline\r
55 Content-Transfer-Encoding: 8bit\r
56 Cc: notmuch@notmuchmail.org\r
57 X-BeenThere: notmuch@notmuchmail.org\r
58 X-Mailman-Version: 2.1.13\r
59 Precedence: list\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: Wed, 04 Jul 2012 02:00:01 -0000\r
70 \r
71 On Tue, 03 Jul 2012 18:27:23 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:\r
72 > On Sat, Jun 23 2012, Peter Wang <novalazy@gmail.com> wrote:\r
73 > > Output Reply-To headers when present in a message.\r
74 > > These were missing in text and json output formats.\r
75\r
76 > I don't see why the Reply-To header is needed, given that we are\r
77 > constructing reply templates, but I guess if someone thinks it's needed\r
78 > I don't see much harm in including it.\r
79 \r
80 I want to see what the sender intended, before hitting reply.\r
81 \r
82 Peter\r