From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: provide various lazy-show options
Date: Mon, 27 Jun 2022 22:02:00 -0300 [thread overview]
Message-ID: <20220628010205.1567784-1-david@tethera.net> (raw)
It is a bit of an unfortunate profusion of options, but it isn't
really clear to me yet if there is one best heuristic for all
use-cases. The overall observation is that for most threads (even up
to several hundred messages), the time to return the query from the
notmuch CLI is much smaller than that to render it in emacs. This
series expands upon some existing ideas of not rendering large text/*
attachments to "lazily" render message bodies for messages satisfying
certain criteria. In one of the introduced test cases this yields
about a 10x speedup. Of course the comparison is not completly fair as
the user probably has to do more work in opening messages to read
them.
I can imagine a couple of different UI improvements. One would be just
choosing some better default values for the parameters discussed in
this series. Another would be to provide a nice ui for temporarily
changing them and re-rendering (perhaps analogous to the limit
commands already present).
next reply other threads:[~2022-06-28 1:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 1:02 David Bremner [this message]
2022-06-28 1:02 ` [PATCH 1/5] perf-test/emacs: test showing longish threads David Bremner
2022-06-28 1:02 ` [PATCH 2/5] emacs/show: optionally insert bodies of "deep messages" lazily David Bremner
2022-06-28 1:02 ` [PATCH 3/5] emacs/show: obey notmuch-show-max-text-part-size for part 0 David Bremner
2022-06-28 1:02 ` [PATCH 4/5] emacs/show: introduce notmuch-show-height-limit David Bremner
2022-06-28 1:02 ` [PATCH 5/5] doc/emacs: add discussion about notmuch-show-perfomance David Bremner
2022-07-14 20:27 ` provide various lazy-show options David Bremner
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=20220628010205.1567784-1-david@tethera.net \
--to=david@tethera.net \
--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).