From: Jed Brown <jed@59A2.org>
To: notmuch <notmuch@notmuchmail.org>
Subject: Emacs client scalability for long, deeply-nested threads
Date: Mon, 23 Mar 2015 12:09:08 -0600 [thread overview]
Message-ID: <87sicv60xn.fsf@jedbrown.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
I occasionally end up with threads containing several hundred messages
and deep nesting. Eventually, displaying them exceeds the default
max-specpdl-size and later max-lisp-eval-depth. These variables can be
increased, but the time required to display the thread stretches to
minutes. Does anyone have suggestions for improving performance in such
scenarios?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next reply other threads:[~2015-03-23 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 18:09 Jed Brown [this message]
2015-03-23 19:59 ` Emacs client scalability for long, deeply-nested threads Michael Hudson-Doyle
2015-03-23 23:26 ` Jed Brown
2015-03-24 19:43 ` David Bremner
2015-03-24 20:12 ` Jed Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sicv60xn.fsf@jedbrown.org \
--to=jed@59a2.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).