Re: Breaking a really long thread

diff --git a/f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838 b/f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838
new file mode 100644 (file)
index 0000000..bd63836
--- /dev/null
+++ b/f4/15abbc4dbc0e3ad7a86a3d4ef3b28a34251838
@@ -0,0 +1,82 @@
+Return-Path:\r
+ <return-5dt29heut3f7yu8ivip6q9jag6@temporary-address.scs.stanford.edu>\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 385886DE02C2\r
+ for <notmuch@notmuchmail.org>; Mon,  4 Apr 2016 22:29:02 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.065\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=0.246,\r
+  RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]\r
+ 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 ILH1B2pmg0Yv for <notmuch@notmuchmail.org>;\r
+ Mon,  4 Apr 2016 22:28:54 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 1EE246DE0243\r
+ for <notmuch@notmuchmail.org>; Mon,  4 Apr 2016 22:28:54 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (localhost.scs.stanford.edu\r
+ [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id\r
+ u355Sjmg019344; Mon, 4 Apr 2016 22:28:45 -0700 (PDT)\r
+Received: (from dm@localhost)\r
+ by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id u355SimH017591;\r
+ Mon, 4 Apr 2016 22:28:44 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+ return-5dt29heut3f7yu8ivip6q9jag6@ta.scs.stanford.edu using -f\r
+From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>\r
+To: Mark Walters <markwalters1009@gmail.com>, Eric <eric@deptj.eu>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: Breaking a really long thread\r
+In-Reply-To: <87k2kd8r6d.fsf@qmul.ac.uk>\r
+References: <c10e501c2baee471cbeeb42aad89a1e966407234-NM@bruno.deptj.eu>\r
+ <87k2kd8r6d.fsf@qmul.ac.uk>\r
+Reply-To: David Mazieres expires 2016-07-03 PDT\r
+ <mazieres-297ctmng4fhr6h6ad8yffa64yi@temporary-address.scs.stanford.edu>\r
+Date: Mon, 04 Apr 2016 22:28:43 -0700\r
+Message-ID: <87wpoc7hf8.fsf@ta.scs.stanford.edu>\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: Tue, 05 Apr 2016 05:29:02 -0000\r
+\r
+Mark Walters <markwalters1009@gmail.com> writes:\r
+\r
+> By default the reference header is hidden. It is controlled by\r
+> message-hidden-headers which you can customize. (Note notmuch adds\r
+> user-agent to this list via notmuch-mua-hidden-header.)\r
+\r
+Thanks for explaining this!  So I posted about one problem, and instead\r
+got a solution to a problem I didn't even realize I had.  Adding:\r
+\r
+  (setq message-hidden-headers (delete "^References:" message-hidden-headers))\r
+\r
+to my eval-after-loaded notmuch-config.el file solved this problem\r
+cold.  No more unintentional References: headers for me.\r
+\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
+David\r