unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Yuan Fu <casouri@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 Vincenzo Pupillo <v.pupillo@gmail.com>,
	Emacs Devel <emacs-devel@gnu.org>,
	 Stefan Kangas <stefankangas@gmail.com>,
	 Dmitry Gutov <dmitry@gutov.dev>
Subject: Re: Tree-sitter central configuration variable
Date: Fri, 29 Nov 2024 12:01:53 -0500	[thread overview]
Message-ID: <jwvo71yyon7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <137AE507-F467-4FB2-83DB-EC621F868C60@gmail.com> (Yuan Fu's message of "Thu, 28 Nov 2024 21:49:33 -0800")

> Since Emacs 29, I see many people ask about how to configure
> tree-sitter modes by setting some variable.

This is not specific to tree-sitter.

> It seems that people much prefer setting a variable than adding
> a major mode hook that calls some functions.

But that boxes them into the subset of possibilities that have been
pre-imagined by those who designed the set of variables.

> What do you guys think about something like this:
>
> (setq treesit-global-configuration
>       '((c-ts-mode
>          ;; Set treesit-font-lock-level to 4
>          (font-lock-level . 4)
>          ;; Disable tree-sitter’s outline support
>          (outline . disable)
>          ;; Enable these features on top of the default ones.
>          (font-lock-enable . (function property variable))
>          ;; Disable these features.
>          (font-lock-disable . (definition))
>          ;; Add extra font-lock rules
>          (font-lock-extra-rules
>           ( :feature 'my-rules
>             :language 'c
>             ((some_query) @some-face)))
>          (simple-indent-extra-rules
>           (c
>            (matcher anchor offset))
>           (d
>            (matcher anchor offset)))
>          )))

Sounds to me like this is inventing a new programming language, just one
that's a lot more restrictive than ELisp.

Is it really better than ELisp which could look like:

    (add-hook 'c-ts-mode-hook #'my-c-ts-mode-preferences)
    (defun my-c-ts-mode-preferences ()
      (setq-local treesit-font-lock-level 4)
      (treesit-outline-mode -1)
      (treesit-font-lock-enable '(function property variable))
      (treesit-font-lock-disable '(definition))
      (treesit-font-lock-add-rules
       '( :feature 'my-rules
          :language 'c
          ((some_query) @some-face)))
      (treesit-indent-add-rules
       '((c
          (matcher anchor offset))
         (d
          (matcher anchor offset)))
      ))

Admittedly, the add-hook/defun dance could be improved, and that would
benefit more than just tree-sitter.  E.g. a new macro like

    (defmacro custom-set-hook (hook &rest body)
      (declare (indent 1) (debug (sexp def-body)))
      (let ((funname (intern (format "custom-set-hook--%s" hook))))
        `(progn (add-hook ',hook #',funnmame)
                (defun ,funname () ,@body))))

> One thing I don’t like is how it handles languages. In this POC
> language-specific settings are nested under the mode. I’m ok with
> mode-language hierarchy, but the nesting adds a lot of nesting levels
> to the variable.  And the language nesting isn’t consistent, some
> settings have language nesting, some don’t.

I don't really understand what you're referring to, but for
`treesit-font-lock-add-rules` would could try and auto-add the `:language`?


        Stefan




  parent reply	other threads:[~2024-11-29 17:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 10:30 Define treesit-font-lock-level as buffer local Vincenzo Pupillo
2024-11-07 11:03 ` Eli Zaretskii
2024-11-07 11:08   ` Vincenzo Pupillo
2024-11-09  8:36     ` Yuan Fu
2024-11-09  8:54       ` Eli Zaretskii
2024-11-10  8:04         ` Yuan Fu
2024-11-23 12:20           ` Eli Zaretskii
2024-11-29  5:49             ` Tree-sitter central configuration variable Yuan Fu
2024-11-29  7:12               ` Eshel Yaron
2024-11-29  8:42                 ` Yuan Fu
2024-11-29  8:04               ` Eli Zaretskii
2024-11-29  9:07                 ` Yuan Fu
2024-11-29 12:02                   ` Eli Zaretskii
2024-11-29 17:01               ` Stefan Monnier [this message]
2024-11-29 17:22                 ` Ship Mints

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=jwvo71yyon7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=casouri@gmail.com \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=v.pupillo@gmail.com \
    /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).