Re: Breaking a really long thread
authorMark Walters <markwalters1009@gmail.com>
Mon, 11 Apr 2016 07:19:23 +0000 (08:19 +0100)
committerW. Trevor King <wking@tremily.us>
Sat, 20 Aug 2016 23:21:35 +0000 (16:21 -0700)
d5/16d7b03ba85ec37c79a840a1c4fc1d0e917e5f [new file with mode: 0644]

diff --git a/d5/16d7b03ba85ec37c79a840a1c4fc1d0e917e5f b/d5/16d7b03ba85ec37c79a840a1c4fc1d0e917e5f
new file mode 100644 (file)
index 0000000..923403e
--- /dev/null
@@ -0,0 +1,128 @@
+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 09F766DE0355\r
+ for <notmuch@notmuchmail.org>; Mon, 11 Apr 2016 00:19:35 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.259\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.259 tagged_above=-999 required=5 tests=[AWL=0.311,\r
+  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7,\r
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]\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 1U1oytyDsIJr for <notmuch@notmuchmail.org>;\r
+ Mon, 11 Apr 2016 00:19:27 -0700 (PDT)\r
+Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com\r
+ [74.125.82.68]) by arlo.cworth.org (Postfix) with ESMTPS id F0D6D6DE0352 for\r
+ <notmuch@notmuchmail.org>; Mon, 11 Apr 2016 00:19:26 -0700 (PDT)\r
+Received: by mail-wm0-f68.google.com with SMTP id l6so19047097wml.3\r
+ for <notmuch@notmuchmail.org>; Mon, 11 Apr 2016 00:19:26 -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=TkE0nN9o9HX00hEHs+OCpwd3CFwNcF/fKvSE9NGPzyE=;\r
+ b=zjcwd8PL/9Ls3XlsgpEooIUbNt/vAEh4Sa4nailUM0Pvj3fjfU9dqPMXscNmYfmR+e\r
+ nAX9tYsz93aWFbZC58HRpIYUKAtXyFIM1to3uHwZ+z5SkBFe9wi2cn+f4IoYeWR14UDZ\r
+ tyPlKSu5w64nPDuI7yC71dyt9hrNmnIUCx6vJ4MfV0IeKEjY4NDQOg1YQy7t4IYxcaQB\r
+ kvOa4jiZyQsoWp7S4myhCPJTZFn+0aQhSvywG5NlSV5X6MFfpPLRazbt8Mxn7/EnjBdT\r
+ yMK41Ahn6lElp3aIFN60S6DXfRIAdqfHSxQcauqBllKnTUjoL16aEXRYT0zVpLwX0/5x\r
+ RoAg==\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=TkE0nN9o9HX00hEHs+OCpwd3CFwNcF/fKvSE9NGPzyE=;\r
+ b=OLZyoFYanmCaHe9BO5FTQ4njEVt54+Qi/2R3hdvGlWlwsTJ+PpBbYOOwthSe2aste8\r
+ M2IaL4xGaNMzwEENeL0qdpF+d6MDD8i3mZf6OQJcrxNNPDZb8rITxNVeitXowZtHMRcW\r
+ 6DtvlFwab/mJwF0zC8JZOGNsdaYq1LdV0spr2E180WmF3l9BLw4QFB9B0XIDX6c154ft\r
+ xpSTJKdhiXdD5BefuCsgVZCblk5SghJzbcYYZ+yGhydJdUn2PDFsPYc6pixPFr8l3Xe8\r
+ S0immO3kjWty9u2Zee/1cgsS+sdgGMsB9fXLXfDdKowVUcCNJLbKFS5ET85Diw8G6RoH\r
+ sy9g==\r
+X-Gm-Message-State:\r
+ AD7BkJKAMoJwbGwvzLOfhCqfN8eSzXFwiCNPbikPq4ozQ6b6bzQvRPzbnmaVIfacw5BmHA==\r
+X-Received: by 10.194.3.45 with SMTP id 13mr22149953wjz.145.1460359165022;\r
+ Mon, 11 Apr 2016 00:19:25 -0700 (PDT)\r
+Received: from localhost ([92.54.140.178])\r
+ by smtp.gmail.com with ESMTPSA id 7sm15795041wmn.7.2016.04.11.00.19.24\r
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Mon, 11 Apr 2016 00:19:24 -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: <87oa9g7vd6.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
+ <87bn5ijthh.fsf@qmul.ac.uk> <87oa9g7vd6.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: Mon, 11 Apr 2016 08:19:23 +0100\r
+Message-ID: <87y48kipdw.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: Mon, 11 Apr 2016 07:19:35 -0000\r
+\r
+\r
+On Mon, 11 Apr 2016, David Bremner <david@tethera.net> wrote:\r
+> Mark Walters <markwalters1009@gmail.com> writes:\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
+>\r
+> Summarizing, I see 3 related changes here\r
+>\r
+> - fixing the code to let-bind message-hidden-headers instead of globally\r
+>   modify it\r
+\r
+I have a patch doing this, but there is one problem that i don't see how\r
+to solve neatly. At the moment we set hidden-headers to the union of\r
+message-hidden-headers and notmuch-mua-hidden-headers. This means that\r
+if the user wants to show a header that is normally one of\r
+message-hidden-headers they have to set message-hidden-headers (ie they\r
+can't just change notmuch-mua-hidden headers).\r
+\r
+If we want it that people can show such a header just by changing a\r
+notmuch variable then I don't see how to do it neatly without breaking\r
+some existing setups.\r
+\r
+Any suggestions?\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+>\r
+> - adding in-reply-to notmuch-mua\r
+>\r
+> - providing a keybinding to toggle visibility of hidden headers that\r
+>   works better than the current use of widen\r
+>\r
+> d\r