From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Hosting tree-sitter pre-built language definitions on ELPA?
Date: Sun, 02 Oct 2022 09:17:00 +0300 [thread overview]
Message-ID: <83k05iagwz.fsf@gnu.org> (raw)
In-Reply-To: <6AC1140D-C4BA-4A39-9474-F127CF79DF28@gmail.com> (message from Yuan Fu on Sat, 1 Oct 2022 21:47:11 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 1 Oct 2022 21:47:11 -0700
>
> Tree-sitter needs language definitions to parse different languages. These language definitions come in the form of dynamic libraries. We can’t bundle them with Emacs since their version must match that of tree-sitter library, and we don’t bundle the tree-sitter library; also they are machine-dependent.
>
> I wonder if we can host pre-built language definitions for languages we provide tree-sitter support OOTB on ELPA, so users can easily download them?
We could, but how is this different from any other optional library
Emacs uses? Users who want to build Emacs with an optional library
are expected to install that library from whatever 3rd-party sources
that make them available. What is different here? Is it really that
hard to download them from the official tree-sitter site?
next prev parent reply other threads:[~2022-10-02 6:17 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
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 [this message]
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=83k05iagwz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--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).