|
From: | Dmitry Gutov |
Subject: | Re: emacs rendering comparisson between emacs23 and emacs26.3 |
Date: | Sun, 5 Apr 2020 22:21:57 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
On 05.04.2020 22:03, Stefan Monnier wrote:
What's the difference between redisplay being slow and it being unable to "keep up"? I don't understand, sorry.If there's already input waiting (because the next event already arrived) at the start of redisplay, then redisplay is short-circuited. Typically, in an auto-repeat circumstance, this will either not happen or happen on a whole batch of repetition. So we say "can't keep up" because processing of one command (including redisplay) takes more time than the interval until the next command.
This agrees with my previous understanding.
And in this case, IIUC, jit-lock is part of redisplay.Yes, it often is when scrolling.
So would you agree that short-circuiting and skipping jit-lock while somebody leans on C-v is a good idea?
[Prev in Thread] | Current Thread | [Next in Thread] |