From 52a2b07a6abb18f946df815d90dad5c78f6dcdfa Mon Sep 17 00:00:00 2001 From: David Mazieres Date: Tue, 5 Apr 2016 22:28:43 +1700 Subject: [PATCH] Re: Breaking a really long thread --- f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838 | 82 +++++++++++++++++++++++ 1 file changed, 82 insertions(+) create mode 100644 f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838 diff --git a/f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838 b/f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838 new file mode 100644 index 000000000..bd6383679 --- /dev/null +++ b/f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838 @@ -0,0 +1,82 @@ +Return-Path: + +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by arlo.cworth.org (Postfix) with ESMTP id 385886DE02C2 + for ; Mon, 4 Apr 2016 22:29:02 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: -2.065 +X-Spam-Level: +X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=0.246, + RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] + autolearn=disabled +Received: from arlo.cworth.org ([127.0.0.1]) + by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id ILH1B2pmg0Yv for ; + Mon, 4 Apr 2016 22:28:54 -0700 (PDT) +Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10]) + by arlo.cworth.org (Postfix) with ESMTPS id 1EE246DE0243 + for ; Mon, 4 Apr 2016 22:28:54 -0700 (PDT) +Received: from market.scs.stanford.edu (localhost.scs.stanford.edu + [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id + u355Sjmg019344; Mon, 4 Apr 2016 22:28:45 -0700 (PDT) +Received: (from dm@localhost) + by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id u355SimH017591; + Mon, 4 Apr 2016 22:28:44 -0700 (PDT) +X-Authentication-Warning: market.scs.stanford.edu: dm set sender to + return-5dt29heut3f7yu8ivip6q9jag6@ta.scs.stanford.edu using -f +From: David Mazieres +To: Mark Walters , Eric , + notmuch@notmuchmail.org +Subject: Re: Breaking a really long thread +In-Reply-To: <87k2kd8r6d.fsf@qmul.ac.uk> +References: + <87k2kd8r6d.fsf@qmul.ac.uk> +Reply-To: David Mazieres expires 2016-07-03 PDT + +Date: Mon, 04 Apr 2016 22:28:43 -0700 +Message-ID: <87wpoc7hf8.fsf@ta.scs.stanford.edu> +MIME-Version: 1.0 +Content-Type: text/plain +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.20 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Tue, 05 Apr 2016 05:29:02 -0000 + +Mark Walters writes: + +> By default the reference header is hidden. It is controlled by +> message-hidden-headers which you can customize. (Note notmuch adds +> user-agent to this list via notmuch-mua-hidden-header.) + +Thanks for explaining this! So I posted about one problem, and instead +got a solution to a problem I didn't even realize I had. Adding: + + (setq message-hidden-headers (delete "^References:" message-hidden-headers)) + +to my eval-after-loaded notmuch-config.el file solved this problem +cold. No more unintentional References: headers for me. + +Arguably, I would say either both the In-Reply-To and the References +header should be hidden or neither. Otherwise, what was happening is +that I was deleting the In-Reply-To header as it was the only one I saw, +and figuring that maybe References was adjusted after the fact based on +In-Reply-To. After all, the message buffer doesn't keep track of the +parent message. + +Unless there's a reason that someone would want to alter In-Reply-To +without altering References, it doesn't make sense to show one without +the other. + +David -- 2.26.2