Re: Breaking a really long thread
authorMark Walters <markwalters1009@gmail.com>
Sat, 9 Apr 2016 22:40:58 +0000 (23:40 +0100)
committerW. Trevor King <wking@tremily.us>
Sat, 20 Aug 2016 23:21:34 +0000 (16:21 -0700)
1a/2e354c0c65215b1e26ce48b720acee0ed1de7c [new file with mode: 0644]

diff --git a/1a/2e354c0c65215b1e26ce48b720acee0ed1de7c b/1a/2e354c0c65215b1e26ce48b720acee0ed1de7c
new file mode 100644 (file)
index 0000000..2b68700
--- /dev/null
@@ -0,0 +1,131 @@
+Return-Path: <markwalters1009@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 51C456DE02BF\r
+ for <notmuch@notmuchmail.org>; Sat,  9 Apr 2016 15:41:12 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.775\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.775 tagged_above=-999 required=5\r
+ tests=[AWL=-0.205, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,\r
+ DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25,\r
+ FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,\r
+ RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 4K29gO3qiJKj for <notmuch@notmuchmail.org>;\r
+ Sat,  9 Apr 2016 15:41:03 -0700 (PDT)\r
+Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com\r
+ [74.125.82.67]) by arlo.cworth.org (Postfix) with ESMTPS id 24B726DE00BD for\r
+ <notmuch@notmuchmail.org>; Sat,  9 Apr 2016 15:41:03 -0700 (PDT)\r
+Received: by mail-wm0-f67.google.com with SMTP id l6so12725626wml.3\r
+ for <notmuch@notmuchmail.org>; Sat, 09 Apr 2016 15:41:03 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=from:to:subject:in-reply-to:references:user-agent:date:message-id\r
+ :mime-version; bh=1AG3MCU9jLq3m+T3TNRxafwXwJV4jPp/7TWk95TOM/A=;\r
+ b=UiB/XacKO14eNmjtfRamSJpCVuYuy9T4mBVzjk1wcrtzEk49q5PG+A0irSZGvf3T9Z\r
+ HfEZ5Yb0koxYWYjC4zTzOHwHkKaLaP0gWxXywXHAEYSUjrKRc0+LXgwVrN8c/WNGFITn\r
+ YCeLray70wJG1zEnTxdDChanffumX9m6uhXavgFxJejQllKWeJ6Is7tptZH7JeSQTnHv\r
+ jv/qNsscRp6B4WFNZUcJb22fUVFkqMw4s41Qw6de+3oi6Gw2+Lh03zIixdZ056V0I0xP\r
+ fFhc+lAuzw9YA+ZW5vxe67UpFSrCZDiwudUFVFeCvRVvZXbzMG3M+qxLZa2XRJ0VgGEU\r
+ KK9A==\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=1e100.net; s=20130820;\r
+ h=x-gm-message-state:from:to:subject:in-reply-to:references\r
+ :user-agent:date:message-id:mime-version;\r
+ bh=1AG3MCU9jLq3m+T3TNRxafwXwJV4jPp/7TWk95TOM/A=;\r
+ b=cEBCKAjzqCjWIipjwxeZz+Wp2C5YqUiktbbvZJtrDmXZJ8LX3K7wJKucjHZnGvMSYH\r
+ JZnf5JbaOuHcrY7bLwLhvElXj2d/Drdkox8rcr1gBvr//Mh65PEwg6GfDx68KFm7vH0g\r
+ TeYZQ+w6AW+l7+kUGDGV5dFl9x6RmsaGEsYrKIItTkbWRePEP6Z78BIcT6/mybX1dTLx\r
+ WJXmp3H1ZPtcFqoDiZqWUIHHTZPXCel/XwGUtIUNSRtwv6Sh3/m0GCpd52Z/YRoiCaPy\r
+ h+Am81U9Km8BODUoaBPa2dvzOsmmZNIcapOcqUWg59gA4zi4VK+DTZjdUWeVarJU4kIU\r
+ GlCg==\r
+X-Gm-Message-State:\r
+ AD7BkJJZeBkwCGspadvH7JMprcT3dvl0J/8lZ3kVDM61KgqlcotUbJ4S8zOJRnZQkQ603w==\r
+X-Received: by 10.28.107.195 with SMTP id a64mr10215985wmi.69.1460241661705;\r
+ Sat, 09 Apr 2016 15:41:01 -0700 (PDT)\r
+Received: from localhost (188.29.66.211.threembb.co.uk. [188.29.66.211])\r
+ by smtp.gmail.com with ESMTPSA id d1sm5896868wjb.47.2016.04.09.15.40.59\r
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Sat, 09 Apr 2016 15:41:01 -0700 (PDT)\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: David Bremner <david@tethera.net>,\r
+ Daniel Kahn Gillmor <dkg@fifthhorseman.net>,\r
+ David Mazieres expires 2016-07-03 PDT\r
+ <mazieres-297ctmng4fhr6h6ad8yffa64yi@temporary-address.scs.stanford.edu>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: Breaking a really long thread\r
+In-Reply-To: <87fuuu3938.fsf@zancas.localnet>\r
+References: <c10e501c2baee471cbeeb42aad89a1e966407234-NM@bruno.deptj.eu>\r
+ <87k2kd8r6d.fsf@qmul.ac.uk> <87wpoc7hf8.fsf@ta.scs.stanford.edu>\r
+ <8760vrm3jk.fsf@alice.fifthhorseman.net> <87fuuu3938.fsf@zancas.localnet>\r
+User-Agent: Notmuch/0.21+17~g6d0b613 (http://notmuchmail.org) Emacs/24.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 09 Apr 2016 23:40:58 +0100\r
+Message-ID: <87bn5ijthh.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 09 Apr 2016 22:41:12 -0000\r
+\r
+\r
+Hi\r
+\r
+On Sat, 09 Apr 2016, David Bremner <david@tethera.net> wrote:\r
+> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:\r
+>\r
+>> On Tue 2016-04-05 01:28:43 -0400, David Mazieres wrote:\r
+>>> Arguably, I would say either both the In-Reply-To and the References\r
+>>> header should be hidden or neither.  Otherwise, what was happening is\r
+>>> that I was deleting the In-Reply-To header as it was the only one I saw,\r
+>>> and figuring that maybe References was adjusted after the fact based on\r
+>>> In-Reply-To.  After all, the message buffer doesn't keep track of the\r
+>>> parent message.\r
+>>>\r
+>>> Unless there's a reason that someone would want to alter In-Reply-To\r
+>>> without altering References, it doesn't make sense to show one without\r
+>>> the other.\r
+>>\r
+>> I think i agree with David here, but the fact is that\r
+>> message-hidden-headers is derived directly from emacs (in message.el),\r
+>> and isn't part of notmuch-emacs at all.\r
+>>\r
+>> Are these changes worth addressing upstream?\r
+>\r
+> Possibly. Although changing defaults is usually a cesspit of\r
+> bikeshedding.  What would we ask, that upstream add In-Reply-To to\r
+> message-hidden-headers?\r
+>\r
+> Related, showing hidden headers doesn't actually work very well:\r
+>\r
+>          http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23252\r
+>\r
+> I thought briefly about overriding the value in notmuch-message-mode,\r
+> perhaps by having a defcustom for notmuch-message-hidden-headers.\r
+\r
+I think we already have this, except it is called\r
+notmuch-mua-hidden-headers. It defaults to '("^User-Agent:").\r
+\r
+I think it would be reasonable to add In-Reply-To to this list.\r
+\r
+However, if I read the code correctly, currently we are changing\r
+message-hidden-headers globally which doesn't feel the right thing to\r
+do. Probably we should do something more like you suggest, and do the\r
+overriding just in notmuch-message-mode.\r
+\r
+Best wishes\r
+\r
+Mark\r