From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Standardizing tree-sitter fontification features
Date: Thu, 24 Nov 2022 21:56:32 -0500 [thread overview]
Message-ID: <jwvsfi7u553.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <D3DD71CE-6844-4EC5-A007-5381841615F3@gmail.com> (Yuan Fu's message of "Thu, 24 Nov 2022 14:16:02 -0800")
> Basic tokens:
>
> delimiter ,.;
> operator = != ||
From the grammar point of view, both of these are simply infix thingies.
Defining precisely the difference between them can be a bit more
delicate, tho. I guess intuitively the idea is that "operator"
corresponds to some kind of run-time operation whereas "delimiter"
serves only to figure out where things start and end but doesn't do
anything in itself.
Not clear where the `=` used for definitions (as in "let x = foo in
bar") should fall. Same for the "," used to construct pairs
or the conjunction/disjunction in Prolog written `,` and `;`
respectively :-)
> string-interpolation f"text {variable}"
> escape-sequence "\n\t\\"
> function every function identifier
I think we definitely need to distinguish a reference/use of a function
from a definition of a function. I do want my function identifiers
highlighted in my function definitions but *not* in my function calls.
> variable every variable identifier
Same here.
[ Note that in many languages (e.g. Scheme and C), functions and
"variables" are the same (i.e. Lisp-1 in the world of Lisp). ]
> type every type identifier
And same here as well.
[ I will spare you the discussion of what should happen for dependently
typed languages where types are "normal" values. ]
> Also, some of the features are very busy, it would be good if we can disable
> they by default. The default value of font-lock-maximum-decoration is t,
> meaning use everything, which is not very helpful...
If you compare the "style" of font-lock rules used until now to those
provide in the new tree-sitter modes, I think it makes sense for
tree-sitter modes to default to "medium" decorations.
Stefan
next prev parent reply other threads:[~2022-11-25 2:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 22:16 Standardizing tree-sitter fontification features Yuan Fu
2022-11-25 1:13 ` Randy Taylor
2022-11-25 6:15 ` Yuan Fu
2022-11-25 19:03 ` Randy Taylor
2022-11-25 20:55 ` Yuan Fu
2022-11-26 3:35 ` Randy Taylor
2022-12-05 21:17 ` Yuan Fu
2022-11-25 8:13 ` Eli Zaretskii
2022-11-25 19:14 ` Randy Taylor
2022-11-26 14:07 ` Stephen Leake
2022-11-25 2:56 ` Stefan Monnier [this message]
2022-11-25 6:34 ` Yuan Fu
2022-11-25 14:52 ` Stefan Monnier
2022-11-26 14:03 ` Stephen Leake
2022-11-26 14:29 ` [SPAM UNSURE] " Stephen Leake
2022-11-26 22:05 ` [SPAM UNSURE] " Yuan Fu
[not found] ` <2AEA8AB6-593E-4D89-AB05-0C8EB2BCE327@gmail.com>
2022-12-03 1:12 ` Yuan Fu
2022-12-03 14:34 ` Mattias Engdegård
2022-12-05 8:58 ` Theodor Thornhill
2022-12-05 10:26 ` Mattias Engdegård
2022-12-05 11:30 ` Theodor Thornhill
2022-12-05 21:02 ` Yuan Fu
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=jwvsfi7u553.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=casouri@gmail.com \
--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).