unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Standardizing tree-sitter fontification features
Date: Sat, 26 Nov 2022 06:03:50 -0800	[thread overview]
Message-ID: <86bkothkxl.fsf@stephe-leake.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")

Yuan Fu <casouri@gmail.com> writes:

> For tree-sitter-based major modes, fontification rules are categorized
> into “features”, which can be individually turned on/off. I think it
> would be good to have a standardized list of common features and their
> precise meaning defined. We’ve been working on these fontification
> rules for some time and arrived at a reasonable baseline, and now it’s
> a good time to discuss and bless it, I think.
>
> Right now we have:
>
> Basic tokens:
>
> delimiter       ,.;
> operator        = != ||
> bracket         []{}()
>
> constant        true, false, null
> number
> keyword
> comment
> string
> string-interpolation    f"text {variable}"
> escape-sequence         "\n\t\\"
> function                every function identifier
> variable                every variable identifier
> type                    every type identifier
> property                a.b  <--- highlight b

namespace would be useful; in some languages, like C++, the syntax
namespace::namespace::object.member makes it clear which identifiers are
namespaces. In others, like Ada the syntax is
namespace.namespace.object.member, so it's not clear.

-- 
-- Stephe



  parent reply	other threads:[~2022-11-26 14:03 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
2022-11-25  6:34   ` Yuan Fu
2022-11-25 14:52     ` Stefan Monnier
2022-11-26 14:03 ` Stephen Leake [this message]
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=86bkothkxl.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --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).