From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@gmail.com>
Cc: luangruo@yahoo.com, casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Hosting tree-sitter pre-built language definitions on ELPA?
Date: Sun, 02 Oct 2022 16:52:27 +0300 [thread overview]
Message-ID: <83sfk61gf8.fsf@gnu.org> (raw)
In-Reply-To: <CAO2hHWa98NUo=m5DWg4fviZS_wcgZzC1jO1oK57S2A46FOjkCg@mail.gmail.com> (message from chad on Sun, 2 Oct 2022 09:37:04 -0400)
> From: chad <yandros@gmail.com>
> Date: Sun, 2 Oct 2022 09:37:04 -0400
> Cc: Po Lu <luangruo@yahoo.com>, casouri@gmail.com, emacs-devel@gnu.org
>
> If I want to build a changed tree-sitter language definition myself, the second-ish step is "install Node.js", and
> I stop there. (Whether this is a sign of taste or curmudgeonliness is left as an exercise for the reader. :-)
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.
> For now, I suspect that something akin to the Windows snapshots on alpha.gnu.org might be a workable
> compromise if the problem actually comes up.
Windows snapshots are provided as a replacement for the GNU/Linux
distros, which are not very widespread on Windows, if they exist at
all. If Emacs installations could be downloaded from, say, the MS
store, I doubt if we'd bother providing binaries.
next prev parent reply other threads:[~2022-10-02 13:52 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 [this message]
2022-10-02 16:36 ` chad
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=83sfk61gf8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=yandros@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).