From: chad <yandros@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Hosting tree-sitter pre-built language definitions on ELPA?
Date: Sun, 2 Oct 2022 12:36:23 -0400 [thread overview]
Message-ID: <CAO2hHWYjF5bZV4+=7YP5pGybsHmqwHTdg63Xk-ftTPC-zgR0Wg@mail.gmail.com> (raw)
In-Reply-To: <83sfk61gf8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On Sun, Oct 2, 2022 at 9:52 AM Eli Zaretskii <eliz@gnu.org> wrote:
> We are not talking about changing the language definitions, we are
> talking about installing the ones provided by tree-sitter. The use
> case you mention is akin to your wanting to modify librsvg -- in which
> case you'd need to start by installing Rust.
>
I _think_ I disagree about that analogy. If I want to use tree-sitter with
a language that is not already somehow installed on my computer, I need a
language definition for it. Right now, I can either install Node.js and
build it myself, or download a binary from github. Is there another option?
IIUC, the current expectation is NOT that an emacs+tree-sitter release will
bundle language definitions for every language we expect the users are
likely to want, or even for, say, the top 10 languages already supported by
emacs outside of treesit. Is that understanding incorrect?
~Chad
[-- Attachment #2: Type: text/html, Size: 1274 bytes --]
next prev parent reply other threads:[~2022-10-02 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 4:47 Hosting tree-sitter pre-built language definitions on ELPA? Yuan Fu
2022-10-02 5:15 ` Po Lu
2022-10-02 5:57 ` Yuan Fu
2022-10-02 6:19 ` Eli Zaretskii
2022-10-02 13:37 ` chad
2022-10-02 13:52 ` Eli Zaretskii
2022-10-02 16:36 ` chad [this message]
2022-10-02 17:06 ` Eli Zaretskii
2022-10-02 22:17 ` Yuan Fu
2022-10-03 15:56 ` Eli Zaretskii
2022-10-04 16:31 ` Yuan Fu
2022-10-03 0:45 ` chad
2022-10-12 10:54 ` Stephen Leake
2022-10-12 13:08 ` Eli Zaretskii
2022-10-02 6:17 ` Eli Zaretskii
2022-10-11 20:51 ` Stefan Monnier
2022-10-12 7:00 ` 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='CAO2hHWYjF5bZV4+=7YP5pGybsHmqwHTdg63Xk-ftTPC-zgR0Wg@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).