From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-devel@gnu.org
Subject: Re: Partly deferred font-locking?
Date: Thu, 12 Jan 2023 15:38:45 +0100 [thread overview]
Message-ID: <877cxrg6mi.fsf@web.de> (raw)
In-Reply-To: <838ri7bzam.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Jan 2023 16:30:41 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> It's a trade-off: you assume that users don't want to see the
> fontifications change in near real-time when editing long lines, but
> that is just an assumption, not necessarily true.
Yes, it really depends on the use case.
My cases so far were all of the category: "expensive" fontification
still happens nearly instantly, hardly noticeable for the human eye, but
slow enough to make scrolling feeling a bit sluggish.
Michael.
next prev parent reply other threads:[~2023-01-12 14:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 17:15 Partly deferred font-locking? Michael Heerdegen
2023-01-11 17:43 ` [External] : " Drew Adams
2023-01-11 18:33 ` Michael Heerdegen
2023-01-11 18:38 ` Drew Adams
2023-01-11 18:49 ` Drew Adams
2023-01-11 19:31 ` Michael Heerdegen
2023-01-11 17:45 ` Eli Zaretskii
2023-01-11 18:36 ` Michael Heerdegen
2023-01-11 19:58 ` Eli Zaretskii
2023-01-12 13:14 ` Michael Heerdegen
2023-01-12 13:45 ` Eli Zaretskii
2023-01-12 14:00 ` Michael Heerdegen
2023-01-12 14:13 ` Eli Zaretskii
2023-01-12 14:26 ` Ihor Radchenko
2023-01-12 14:30 ` Ihor Radchenko
2023-01-12 14:36 ` Eli Zaretskii
2023-01-12 14:44 ` Ihor Radchenko
2023-01-12 15:11 ` Eli Zaretskii
2023-01-12 15:40 ` Ihor Radchenko
2023-01-12 14:30 ` Eli Zaretskii
2023-01-12 14:36 ` Ihor Radchenko
2023-01-12 14:38 ` Michael Heerdegen [this message]
2023-01-12 14:33 ` Michael Heerdegen
2023-01-12 15:51 ` Eli Zaretskii
2023-01-12 16:02 ` Michael Heerdegen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cxrg6mi.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yantar92@posteo.net \
/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://git.savannah.gnu.org/cgit/emacs.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).