unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Felix <felix.dick@web.de>
To: emacs-devel@gnu.org
Subject: Re: Tree-sitter doc question
Date: Thu, 08 Dec 2022 16:08:39 +0100	[thread overview]
Message-ID: <87tu26rklo.fsf@web.de> (raw)
In-Reply-To: <835yem2bal.fsf@gnu.org>


Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Thu, 8 Dec 2022 15:52:46 +0100
>> From: Ergus <spacibba@aol.com>
>>
>> >The modes that rely on it know how to check that.
>> >
>> Yes, but as I was trying to use it in C I didn't know if it was actually
>> working or not as I don't see any change.
>
> You need to turn on c-ts-mode manually, it is an opt-in feature (and
> will probably remain like that in Emacs 29).
>
>> >The colors are our faces, so the answer is "neither".
>> >
>> I know; maybe I needed to be more specific. As I don't know if it is
>> working I don't know who was setting the syntax info.
>
> The faces are set based on the results of parsing by the tree-sitter
> library.

What would be the recommended way to enable the *-ts-mode for a certain
language?
Adding a hook to a major-mode to enable another major-mode seems a bit
backward. This is what i did first, now i added entries to auto-mode-alist.
It would be nice to have an customization variable that controls which
major-modes are replaced.
For more user feedback, it would be beneficial to have an easy way to
enable and try tree-sitter.



  reply	other threads:[~2022-12-08 15:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221208141247.36l2j3bxggslsykl.ref@Ergus>
2022-12-08 14:12 ` Tree-sitter doc question Ergus
2022-12-08 14:38   ` Eli Zaretskii
     [not found]     ` <20221208145246.3iq7ehnxdii5xgqq@Ergus>
2022-12-08 14:57       ` Eli Zaretskii
2022-12-08 15:08         ` Felix [this message]
2022-12-08 15:44           ` Eli Zaretskii
2022-12-08 16:05             ` Stefan Kangas
2022-12-08 16:24               ` Juanma Barranquero
2022-12-08 16:29                 ` Felix
2022-12-08 17:01                   ` [External] : " Drew Adams
2022-12-08 17:39                   ` Eli Zaretskii
2022-12-08 17:35                 ` Eli Zaretskii
2022-12-08 17:43           ` Stefan Monnier
2022-12-09  8:33 Pedro Andres Aranda Gutierrez
2022-12-09 12:10 ` Eli Zaretskii
2022-12-10  7:29   ` Pedro Andres Aranda Gutierrez
2022-12-10  8:46     ` Eli Zaretskii
2022-12-10 11:14       ` Pedro Andres Aranda Gutierrez
2022-12-10 15:29         ` João Paulo Labegalini de Carvalho
2022-12-11  8:31           ` Pedro Andres Aranda Gutierrez
2022-12-11 22:03             ` Yuan Fu
2022-12-12  8:57               ` Pedro Andres Aranda Gutierrez
2022-12-12 16:36         ` Eric S Fraga
2022-12-12 17:59           ` Stefan Monnier
2022-12-12 18:11             ` Eli Zaretskii
2022-12-12 18:20               ` Stefan Monnier
2022-12-12 18:32                 ` Óscar Fuentes
2022-12-12 18:52                   ` Juanma Barranquero
2022-12-12 19:20                     ` Óscar Fuentes
2022-12-12 19:37                       ` Eli Zaretskii
2022-12-12 22:50                       ` Tim Cross
2022-12-12 23:34                         ` João Paulo Labegalini de Carvalho
2022-12-13  3:25                           ` Tim Cross
2022-12-12 19:19                 ` Fraga, Eric

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=87tu26rklo.fsf@web.de \
    --to=felix.dick@web.de \
    --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).