From: Randy Taylor <dev@rjt.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Standardizing tree-sitter fontification features
Date: Fri, 25 Nov 2022 19:14:59 +0000 [thread overview]
Message-ID: <d8YWY2drOoXk8KkMQ4cy6d8x2p--7Uun-Exu_ilZ_7WdNY1rf3MxV6rdOTyw-tmAcpIJ-miXSWuXkO9edGEYXauJ8U4y3XWdw4ozHVKilO8=@rjt.dev> (raw)
In-Reply-To: <83o7svv4cy.fsf@gnu.org>
On Friday, November 25th, 2022 at 03:13, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Fri, 25 Nov 2022 01:13:46 +0000
>
> > From: Randy Taylor dev@rjt.dev
> > Cc: emacs-devel emacs-devel@gnu.org
> >
> > On Thursday, November 24th, 2022 at 17:16, Yuan Fu casouri@gmail.com wrote:
> >
> > I wonder if assignment and definition are really worth having (and would prefer to do without them), since they should be covered by the variable, function, type and property features.
>
>
> AFAIU, this is about the difference between defining a function and calling
> it. The distinction could be useful, at least in some cases. We could make
> this off by default, of course, but I don't think we should ignore the
> distinction.
Yes, in my mind the variable, function, etc. features would cover everything but it's clear people want more control over that aspect. We could give them different faces, but that would require making more faces which probably isn't desired. The only unfortunate thing, as I asked Yuan, is we may end up with duplication (depending on how we do it). Assignment and declaration will have a fair bit of overlap with the variable and function features.
next prev parent reply other threads:[~2022-11-25 19:14 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 [this message]
2022-11-26 14:07 ` Stephen Leake
2022-11-25 2:56 ` Stefan Monnier
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='d8YWY2drOoXk8KkMQ4cy6d8x2p--7Uun-Exu_ilZ_7WdNY1rf3MxV6rdOTyw-tmAcpIJ-miXSWuXkO9edGEYXauJ8U4y3XWdw4ozHVKilO8=@rjt.dev' \
--to=dev@rjt.dev \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--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).