From: Ihor Radchenko <yantar92@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>,
Theodor Thornhill <theo@thornhill.no>
Subject: Re: Recent updates to tree-sitter branch
Date: Sun, 25 Sep 2022 14:17:24 +0800 [thread overview]
Message-ID: <87wn9srn9n.fsf@localhost> (raw)
In-Reply-To: <C6117703-7C33-4DB5-A556-5EDF37511374@gmail.com>
Yuan Fu <casouri@gmail.com> writes:
> 2. Although treesit-font-lock-settings didn’t change, treesit-font-lock-defaults is abandoned. You are also now supposed to use treesit-font-lock-rules to build the queries and set it to treesit-font-lock-settings. It is much cleaner than setting treesit-font-lock-settings manually.
I am not sure if it has been discussed, but may I ask a few questions
regarding treesit-font-lock-rules.
If my understanding is correct, the font-lock rules are somewhat
equivalent font-lock-keywords, but much more limited.
font-lock-keywords elements can have a form of
MATCHER
(MATCHER . SUBEXP)
(MATCHER . FACENAME)
(MATCHER . HIGHLIGHT)
(MATCHER HIGHLIGHT ...)
(eval . FORM)
where MATCHER is either a regexp or a function.
treesit-font-lock-rules rules take a form of
(MATCHER FACENAME) or (MATCHER FUNCTION)
where MATCHER can only be a query.
Is there any reason why MATCHER in treesit-font-lock-rules cannot be a
function with access to the fontified node? It will allow more flexible
fontification, when programmatic query can be used to decide the
fontification.
Further, can OVERRIDE FLAG of the MATCH-HIGHLIGHT as in
font-lock-keywords be supported?
"If OVERRIDE is t, existing fontification can be overwritten. If
keep, only parts not already fontified are highlighted. If prepend or
append, existing fontification is merged with the new, in which the new
or existing fontification, respectively, takes precedence."
--
Ihor Radchenko,
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
next prev parent reply other threads:[~2022-09-25 6:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 4:27 Recent updates to tree-sitter branch Yuan Fu
2022-09-25 6:17 ` Ihor Radchenko [this message]
2022-09-26 8:35 ` Yuan Fu
2022-09-26 9:43 ` Ihor Radchenko
2022-09-27 22:28 ` Yuan Fu
2022-09-29 4:01 ` Ihor Radchenko
2022-09-30 21:03 ` Yuan Fu
2022-10-01 4:20 ` Ihor Radchenko
2022-10-02 3:46 ` Yuan Fu
2022-10-02 7:33 ` Ihor Radchenko
2022-10-02 22:54 ` Yuan Fu
2022-10-03 5:58 ` Ihor Radchenko
2022-10-04 16:58 ` Yuan Fu
2022-09-29 10:13 ` Aurélien Aptel
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=87wn9srn9n.fsf@localhost \
--to=yantar92@gmail.com \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=theo@thornhill.no \
/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).