From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Tree-sitter doc question
Date: Fri, 09 Dec 2022 14:10:19 +0200 [thread overview]
Message-ID: <83y1rgzsk4.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk8O3bwWm64HadBzWXM8ZwRmaxPTh2N7bZdBsFWkSVwe0w@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Fri, 9 Dec 2022 09:33:11 +0100)
> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Fri, 9 Dec 2022 09:33:11 +0100
>
> >User-level documentation was not yet written, we will do that a bit
> >later.
>
> To add to Ergus' quick question. How long would it take to write a couple
> of lines for the not-yet-informed with *all* steps to get a tree-sitter mode
> up and running? I don't know, python-ts-mode, c-ts-mode...
> Maybe that would encourage more users/testers and thus (hopefully) make
> tree-sitter more tested, usable, popular, (you name it)
?? These modes have doc strings, so it isn't like they aren't
documented at all.
And setting them up boils down to just turning them ON, something the
users who follow the development branches should know already. Why
did you assume you'd need something beyond "M-x python-ts-mode RET"?
next prev parent reply other threads:[~2022-12-09 12:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 8:33 Re: Tree-sitter doc question Pedro Andres Aranda Gutierrez
2022-12-09 12:10 ` Eli Zaretskii [this message]
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
[not found] <20221208141247.36l2j3bxggslsykl.ref@Ergus>
2022-12-08 14:12 ` 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
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:39 ` Eli Zaretskii
2022-12-08 17:35 ` Eli Zaretskii
2022-12-08 17:43 ` Stefan Monnier
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=83y1rgzsk4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=paaguti@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).