From: Jani Nikula <jani@nikula.org>
To: David Bremner <david@tethera.net>,
Johan Parin <johanparin@gmail.com>,
notmuch@notmuchmail.org
Cc: Johan Parin <johan.parin@gmail.com>
Subject: Re: [PATCH] Fix format_headers_sprinter to return all headers
Date: Sun, 10 Nov 2019 11:49:04 +0200 [thread overview]
Message-ID: <87bltkawof.fsf@nikula.org> (raw)
In-Reply-To: <87d0e0vllf.fsf@tethera.net>
On Sat, 09 Nov 2019, David Bremner <david@tethera.net> wrote:
> Jani Nikula <jani@nikula.org> writes:
>
>> On Sat, 09 Nov 2019, Johan Parin <johanparin@gmail.com> wrote:
>>> Modify format_headers_sprinter so that it returns all headers in the
>>> sexp, instead of a fixed set of headers.
>>
>> I have to deal with plenty of long threads that already take a very long
>> time to open in notmuch-emacs. How's this going to impact the emacs
>> interface performance? For example the patch mail I'm replying to has
>> more header content than body content. There are tons of headers that I
>> can't imagine being useful to anyone.
>
> Can we benchmark this somehow? I think we have suitable threads in the
> LKML corpus, but the challenge is timing emacs in some sensible way.
notmuch-emacs performance tests? :o
I can of course try this stuff to get a gut feeling, but it's subjective
and doesn't really scale. :)
BR,
Jani.
next prev parent reply other threads:[~2019-11-10 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 17:44 [PATCH] Fix format_headers_sprinter to return all headers Johan Parin
2019-11-09 19:19 ` Jani Nikula
2019-11-09 20:30 ` David Bremner
2019-11-10 9:49 ` Jani Nikula [this message]
2019-11-09 20:32 ` Johan Parin
2019-11-10 9:46 ` Jani Nikula
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=87bltkawof.fsf@nikula.org \
--to=jani@nikula.org \
--cc=david@tethera.net \
--cc=johan.parin@gmail.com \
--cc=johanparin@gmail.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).