From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: [External] : Partly deferred font-locking?
Date: Wed, 11 Jan 2023 20:31:39 +0100 [thread overview]
Message-ID: <87v8lc27hg.fsf@web.de> (raw)
In-Reply-To: CO6PR10MB5473162671E0946D97ECA974F3FC9@CO6PR10MB5473.namprd10.prod.outlook.com
Drew Adams <drew.adams@oracle.com> writes:
> If that symlink font-lock rule is in a higher level
> then that already should provide a way to avoid its
> cost. IOW, IIUC, just choosing not to fontify
> symlinks should take care of that particular cost.
> (But maybe I've misunderstood you.)
"What" and "how" are coupled: dired now indicates the type of symlink
targets by color (attached to the symlink). Also broken symlinks are
highlighted specially. To do that font-lock has to consult the file
system. The rest of dired fontification is purely text based AFAIK.
But this was only an example to demonstrate the purpose of my question.
Michael.
next prev parent reply other threads:[~2023-01-11 19:31 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 [this message]
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
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=87v8lc27hg.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
/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).