1 Return-Path: <amdragon@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 EF9BD431FD0
\r
6 for <notmuch@notmuchmail.org>; Thu, 9 Jun 2011 18:58:43 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001,
\r
13 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 N11AFFwlAJDv for <notmuch@notmuchmail.org>;
\r
17 Thu, 9 Jun 2011 18:58:43 -0700 (PDT)
\r
18 Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com
\r
19 [209.85.216.174]) (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 37805431FB6
\r
22 for <notmuch@notmuchmail.org>; Thu, 9 Jun 2011 18:58:43 -0700 (PDT)
\r
23 Received: by qyk7 with SMTP id 7so3222627qyk.5
\r
24 for <notmuch@notmuchmail.org>; Thu, 09 Jun 2011 18:58:42 -0700 (PDT)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
\r
26 h=domainkey-signature:mime-version:sender:in-reply-to:references:date
\r
27 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
\r
28 bh=wJJhUG0A495MjgfrsmEzEvo8rvA49cq+I5IvmNjGx5Q=;
\r
29 b=thZv3WISlCjUnXrrGSTe87nDGivHKX62+W1qofzi650QCSKAl1rOw7aVP54PL+QOe4
\r
30 1TdoS25UPd10dMiHYWM4jPqJOk8+YIF2zW4kEa9IEL/tJZqQeNAHUVw9YHZCA5hP0gOf
\r
31 M46r91hG3eMbLhvAdU+znNhAQ9kgdmLjQK8Bo=
\r
32 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
\r
33 h=mime-version:sender:in-reply-to:references:date
\r
34 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
\r
35 b=NfCUkhukjcyJq2sV2ZtJWJKto/WqCy83gn6/KeB8Grk131kpKYHfnXoBlwUmf61BIK
\r
36 v6ZyvElA6Ojpsh/eoVDJITWA4iTiQsvonhtu2KNWxfHmW5/uzR3xKBo9fnN/guUxrgg2
\r
37 DzWZOyDOu9pAXPWAoBxWO+2MAcIMpKRUAcWBs=
\r
39 Received: by 10.229.114.200 with SMTP id f8mr1114004qcq.68.1307671121261; Thu,
\r
40 09 Jun 2011 18:58:41 -0700 (PDT)
\r
41 Sender: amdragon@gmail.com
\r
42 Received: by 10.229.211.148 with HTTP; Thu, 9 Jun 2011 18:58:41 -0700 (PDT)
\r
43 In-Reply-To: <1307561409-5646-1-git-send-email-jrollins@finestructure.net>
\r
44 References: <1307320169-29905-4-git-send-email-jrollins@finestructure.net>
\r
45 <1307561409-5646-1-git-send-email-jrollins@finestructure.net>
\r
46 Date: Thu, 9 Jun 2011 21:58:41 -0400
\r
47 X-Google-Sender-Auth: JTw3SS6OIsGhRJv9i-RveRbXjCM
\r
48 Message-ID: <BANLkTikT9HgD=UijeBWLOEVz+rbKPtmFZQ@mail.gmail.com>
\r
49 Subject: Re: tweaks for handling parts in reply
\r
50 From: Austin Clements <amdragon@mit.edu>
\r
51 To: Jameson Graef Rollins <jrollins@finestructure.net>
\r
52 Content-Type: text/plain; charset=ISO-8859-1
\r
53 Cc: Notmuch Mail <notmuch@notmuchmail.org>
\r
54 X-BeenThere: notmuch@notmuchmail.org
\r
55 X-Mailman-Version: 2.1.13
\r
57 List-Id: "Use and development of the notmuch mail system."
\r
58 <notmuch.notmuchmail.org>
\r
59 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
60 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
61 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
62 List-Post: <mailto:notmuch@notmuchmail.org>
\r
63 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
64 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
65 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
66 X-List-Received-Date: Fri, 10 Jun 2011 01:58:44 -0000
\r
68 It's too bad this requires lots of special-casing. I dug into mutt,
\r
69 hoping to find some simpler way to choose what to reply to, but all I
\r
70 found was a far more complicated collection of heuristics (see
\r
71 mutt_body_handler if you're interested).
\r
73 Should reply *ever* include a "Non-text part" message? It certainly
\r
74 doesn't help the receiver of the reply and presumably the sender will
\r
75 either notice that a part is missing if they care about it, or
\r
76 probably miss the Non-text part message anyway if they don't.
\r
78 On Wed, Jun 8, 2011 at 3:30 PM, Jameson Graef Rollins
\r
79 <jrollins@finestructure.net> wrote:
\r
80 > This is a small set of tweaks to remove unneccessary "Non-text part:"
\r
81 > lines in reply, for parts that really don't need to be mentioned.
\r
83 > This patch set is not really related to the series that it is being
\r
84 > sent in reply to, but it has been worked on top of the message/rfc822
\r
85 > rework of the multipart test, so it's being sent in reply to that
\r
90 > _______________________________________________
\r
91 > notmuch mailing list
\r
92 > notmuch@notmuchmail.org
\r
93 > http://notmuchmail.org/mailman/listinfo/notmuch
\r