From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: shipmints@gmail.com, monnier@iro.umontreal.ca,
v.pupillo@gmail.com, emacs-devel@gnu.org, stefankangas@gmail.com,
dmitry@gutov.dev
Subject: Re: Tree-sitter central configuration variable
Date: Tue, 03 Dec 2024 15:14:57 +0200 [thread overview]
Message-ID: <865xo03o32.fsf@gnu.org> (raw)
In-Reply-To: <DB185D61-13AB-4D2E-B951-CDEEC1498FB9@gmail.com> (message from Yuan Fu on Mon, 2 Dec 2024 22:40:56 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Mon, 2 Dec 2024 22:40:56 -0800
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 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>
>
> Maybe what we really need is a good guide/manual section on installing and configuring tree-sitter major modes. I wrote a detailed guide for writing tree-sitter major modes, but didn’t write one for installing and configuring tree-sitter major modes.
We might consider doing that once we figure out what is the best way
of installing and configuring these modes ;-) For now, we are
discussing the different alternatives for doing so, and have not yet
reached an agreement, AFAIU, let alone implemented it.
prev parent reply other threads:[~2024-12-03 13:14 UTC|newest]
Thread overview: 17+ 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
2024-11-29 17:22 ` Ship Mints
2024-12-03 6:40 ` Yuan Fu
2024-12-03 13:14 ` Eli Zaretskii [this message]
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=865xo03o32.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=shipmints@gmail.com \
--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).