Re: Emacs client scalability for long, deeply-nested threads

diff --git a/c9/e0a69592c144ee5533d7faad581509a7cf13f8 b/c9/e0a69592c144ee5533d7faad581509a7cf13f8
new file mode 100644 (file)
index 0000000..27f7513
--- /dev/null
+++ b/c9/e0a69592c144ee5533d7faad581509a7cf13f8
@@ -0,0 +1,83 @@
+Return-Path: <michael.hudson@canonical.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 olra.theworths.org (Postfix) with ESMTP id 1C8A1431FD4\r
+       for <notmuch@notmuchmail.org>; Mon, 23 Mar 2015 12:59:23 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 1.738\r
+X-Spam-Level: *\r
+X-Spam-Status: No, score=1.738 tagged_above=-999 required=5\r
+       tests=[DNS_FROM_AHBL_RHSBL=2.438, RCVD_IN_DNSWL_LOW=-0.7]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id hBwsf8uWVwVC for <notmuch@notmuchmail.org>;\r
+       Mon, 23 Mar 2015 12:59:19 -0700 (PDT)\r
+Received: from mail-we0-f177.google.com (mail-we0-f177.google.com\r
+       [74.125.82.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id AF0E3431FD2\r
+       for <notmuch@notmuchmail.org>; Mon, 23 Mar 2015 12:59:19 -0700 (PDT)\r
+Received: by weop45 with SMTP id p45so146893516weo.0\r
+       for <notmuch@notmuchmail.org>; Mon, 23 Mar 2015 12:59:17 -0700 (PDT)\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:mime-version:in-reply-to:references:date\r
+       :message-id:subject:from:to:cc:content-type;\r
+       bh=DlMwCWiQx5UYfceoW8ELMko1A8584PGv7Nv9xmKkdz8=;\r
+       b=f4iw4u2WdUAD9KMRbg8MOahbX2w+FUgkFBYicMh/w0JbvAIgWZwf9yxJIVqd4tSl21\r
+       VULhylZjIBU/mpC1NtZ5cXKTaQgICCnNV8qh87maWnwjaGD9tdlE+X5dKczKRF6P9AYb\r
+       uNyJpBHDOtp1eRTA+rOBj34xzfWM+Nj2oqWcfS6BnPsIDWBnkdI07Gnbm/AkBlePnElk\r
+       md9TmH6WdXUIX0Gm8fk0LotXQUGVopufb2b87mFQdF+9nlu6MIo39KUpodNPPHei7kAT\r
+       1vojH0v7qscVnJkrVe4XZl460Vd1DalWrcI6aj+TGd3eX1vhDn8qBIcKGg4/IQtAYjpD\r
+       A53Q==\r
+X-Gm-Message-State:\r
+ ALoCoQncgG1/rpA/7/II/GqmsFAsCZVOQ7cH19oOX6F4tb9KxIoLSLXDTGvMNXDriOZyuIYBBXgw\r
+MIME-Version: 1.0\r
+X-Received: by 10.180.80.101 with SMTP id q5mr15699873wix.83.1427140757433;\r
+       Mon, 23 Mar 2015 12:59:17 -0700 (PDT)\r
+Received: by 10.180.104.195 with HTTP; Mon, 23 Mar 2015 12:59:17 -0700 (PDT)\r
+In-Reply-To: <87sicv60xn.fsf@jedbrown.org>\r
+References: <87sicv60xn.fsf@jedbrown.org>\r
+Date: Tue, 24 Mar 2015 08:59:17 +1300\r
+Message-ID:\r
+ <CAJ8wqtfhJs7t6GvAz=CCCWZ5=ZCHnTyAkXZ5-7Z_pnW6s9tM-w@mail.gmail.com>\r
+Subject: Re: Emacs client scalability for long, deeply-nested threads\r
+From: Michael Hudson-Doyle <michael.hudson@canonical.com>\r
+To: Jed Brown <jed@59a2.org>\r
+Content-Type: text/plain; charset=UTF-8\r
+Cc: notmuch <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://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: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 23 Mar 2015 19:59:23 -0000\r
+\r
+I have encountered this too.  A C-u before entering the thread helps\r
+(this means already read messages are not rendered I think), as does a\r
+M-x notmuch-show-toggle-thread-indentation .  Something less manual\r
+would be nice, I guess...\r
+\r
+On 24 March 2015 at 07:09, Jed Brown <jed@59a2.org> wrote:\r
+> I occasionally end up with threads containing several hundred messages\r
+> and deep nesting.  Eventually, displaying them exceeds the default\r
+> max-specpdl-size and later max-lisp-eval-depth.  These variables can be\r
+> increased, but the time required to display the thread stretches to\r
+> minutes.  Does anyone have suggestions for improving performance in such\r
+> scenarios?\r
+>\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
+>\r