|
From: | Herman |
Subject: | bug#66764: 29.1; Emacs scrolls for "(goto-char (point-max))" instead of jumping |
Date: | Fri, 27 Oct 2023 11:43:28 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.1 |
On 10/27/23 08:50, Eli Zaretskii wrote:
As far as I understand, if the buffer is fully font-locked, then this function won't be called again, unless the buffer is modified. So this shouldn't be a problem. But even if this is not true, I've been using this setting for a long time, I didn't notice any performance problems with it.AFAIU, the font-lock-keywords setting above causes the display engine to call this function every time it moves across some chunk of text, which slows down redisplay. This shows with scroll-conservatively set to a large value because Emacs then attempts to find the minimum amount of scrolling the screen in order to bring point into the view.
This setting comes from a package named hl-todo. I believe it is done this way so it only highlights TODO items which are in comments/strings. Maybe there is a better way to achieve this, I don't know.It is a known fact that modes which use advanced font-lock settings should adapt to the long-line situation (when the function long-line-optimizations-p returns non-nil)
I turned off long-line optimizations instead, because it causes other problems as well (mentioned in my previous email).so I think you should modify your font-lock settings to avoid this problem in that case.
[Prev in Thread] | Current Thread | [Next in Thread] |