From: Jed Brown <jed@59a2.org>
To: Michael Hudson-Doyle <michael.hudson@canonical.com>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: Emacs client scalability for long, deeply-nested threads
Date: Mon, 23 Mar 2015 17:26:55 -0600 [thread overview]
Message-ID: <874mpb5m80.fsf@jedbrown.org> (raw)
In-Reply-To: <CAJ8wqtfhJs7t6GvAz=CCCWZ5=ZCHnTyAkXZ5-7Z_pnW6s9tM-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
Michael Hudson-Doyle <michael.hudson@canonical.com> writes:
> I have encountered this too. A C-u before entering the thread helps
> (this means already read messages are not rendered I think), as does a
> M-x notmuch-show-toggle-thread-indentation .
Thanks, Michael. This does help, though it makes it hard to interpret
context. I'd love a solution that does not degrade utility so
drastically.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-03-23 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 18:09 Emacs client scalability for long, deeply-nested threads Jed Brown
2015-03-23 19:59 ` Michael Hudson-Doyle
2015-03-23 23:26 ` Jed Brown [this message]
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=874mpb5m80.fsf@jedbrown.org \
--to=jed@59a2.org \
--cc=michael.hudson@canonical.com \
--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).