From: emacsq via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Why is jit-lock-stealth-time nil by default?
Date: Thu, 17 Feb 2022 06:58:09 +0000 [thread overview]
Message-ID: <JtCtsb7d-qX3FsAmZvneVgWH6D3-193MEyrQ8GxJI10xI2C3HGjqGn8q-uxXrqCQOeEohEWWngJfG-Msj63XlJcV_ynUZflLZsVXdwJaJ7o=@protonmail.com> (raw)
In-Reply-To: <E1aDPrFtTh4_Nr1-oD01nSg3SNZND7L5gh8jDON4n8PQo-WYbdbEC8K972m3Ddt-0YxumonhIZVDMsu7P4BzBKrtza0tqvEfy9P0YephqF4=@protonmail.com>
> That shouldn't happen. Emacs uses a JIT fontification feature, which
> is turned on by default, and which should make sure any part of the
> buffer is always fontified before it is displayed.
Is it also true for programmatic features, that is if the user himself doesn't visit those parts, only elisp routines go there and show parts of the buffer? E.g. 'peek' features which fetch unvisited parts of a buffer and show them to the user in a tooltip? I thought JIT does not fontificates those parts.
------- Original Message -------
On Thursday, February 17th, 2022 at 7:26 AM, emacsq <laszlomail@protonmail.com> wrote:
> I use commands which can show unvisited parts of a buffer and I find it
> annoying when those parts are not fontified.
>
> I looked into it and found stealth font locking which performs fontification
> of those parts when the user is idle.
>
> But jit-lock-stealth-time is nil by default. Is there a reason for this? It's a useful
> feature and today's computers have plenty of idle time, so why is not enabled
> out of the box?
next prev parent reply other threads:[~2022-02-17 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 6:26 Why is jit-lock-stealth-time nil by default? emacsq via Users list for the GNU Emacs text editor
2022-02-17 6:44 ` Eli Zaretskii
2022-02-17 6:58 ` emacsq via Users list for the GNU Emacs text editor [this message]
2022-02-17 7:58 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='JtCtsb7d-qX3FsAmZvneVgWH6D3-193MEyrQ8GxJI10xI2C3HGjqGn8q-uxXrqCQOeEohEWWngJfG-Msj63XlJcV_ynUZflLZsVXdwJaJ7o=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=laszlomail@protonmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.