From: Rainer Gemulla <rgemulla@uni-mannheim.de>
To: David Bremner <david@tethera.net>, Rainer Gemulla <hqn1@gmx.de>,
notmuch@notmuchmail.org
Subject: Re: notmuch-show-mode: slowdown due to redisplay
Date: Wed, 08 Dec 2021 16:14:01 +0100 [thread overview]
Message-ID: <8735n3f7t2.fsf@macho> (raw)
In-Reply-To: <87h7bjuqdv.fsf@tethera.net>
[-- Attachment #1.1: Type: text/plain, Size: 1101 bytes --]
>> I've tracked it down: it happens when multiple large images are
>> attached to the email (and displayed inline) and global-hl-line-mode
>> is turned on. The former slows down redisplay, the latter makes
>> redisplay do something with every cursor movement.
>
> I made a test message with 10 copies of a (black and white) 3k x 3k
> jpeg image, enabled global-hl-line-mode, but I don't notice any
> navigation problems. I wonder if there could be an interaction with some
> other package? Or do I need bigger / more images?
It's not consistent, apparently. I do have a message (with 2 images and multiple PDF attachments) where it looks like this:
15095 97% - notmuch-show-command-hook
15095 97% - redisplay
16 0% - redisplay_internal (C function)
16 0% - eval
16 0% spaceline-ml-main
when global-hl-line-mode is on. Unfortunately, I cannot share this message. Generally, it only happens when one of the attached images is visible in the window.
If I stumble across this problem with a message that I can share, I'll post it here.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2021-12-09 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 8:38 notmuch-show-mode: slowdown due to redisplay Rainer Gemulla
2021-12-07 16:56 ` David Bremner
2021-12-08 11:15 ` Rainer Gemulla
2021-12-08 14:23 ` David Bremner
2021-12-08 15:14 ` Rainer Gemulla [this message]
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=8735n3f7t2.fsf@macho \
--to=rgemulla@uni-mannheim.de \
--cc=david@tethera.net \
--cc=hqn1@gmx.de \
--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).