unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, emacs-devel@gnu.org
Subject: Re: Partly deferred font-locking?
Date: Thu, 12 Jan 2023 14:36:11 +0000	[thread overview]
Message-ID: <87lem795wk.fsf@localhost> (raw)
In-Reply-To: <838ri7bzam.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> More complex fontification may stumble on _editing_ long lines - if
>> fontification is performed line-by-line, long lines can slow down the
>> performance significantly (which is a known problem). It is often
>> a reasonable trade-off to defer re-fontification while editing a long
>> line and re-fontify it later. I have stumbled upon this issue myself in
>> my parser-based fontification for Org.
>
> 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.

You are right. However, I am pretty sure that many users will prefer
having font-lock stop ongoing fontification when they try to enter key
sequence. Or, at least, when they try to enter a key and fontification
is taking more than something like `jit-lock-non-stealth-time' variable
(defaulting to ~0.1 sec).

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2023-01-12 14:36 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 [this message]
2023-01-12 14:38                   ` Michael Heerdegen
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=87lem795wk.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).