From: Yuan Fu <casouri@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Hosting tree-sitter pre-built language definitions on ELPA?
Date: Sat, 1 Oct 2022 22:57:41 -0700 [thread overview]
Message-ID: <5E327D85-FFF2-4633-98B7-B53EC9A8038B@gmail.com> (raw)
In-Reply-To: <87pmfa4xib.fsf@yahoo.com>
> On Oct 1, 2022, at 10:15 PM, Po Lu <luangruo@yahoo.com> wrote:
>
> Yuan Fu <casouri@gmail.com> writes:
>
>> 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.
>
> If that's a problem, perhaps we could import the tree-sitter library
> into the Emacs tree, like the XMenu library currently is.
Tree-sitter is designed to be embedded, so it’s small and has no dependencies. But tree-sitter could release a new version and then language definitions now uses that new version, while Emacs is still using the old version of tree-sitter. IMHO it is best to keep them (tree-sitter library and language definitions) external since that’ll be easier to maintain, and Emacs don’t depend on tree-sitter to function.
Yuan
next prev parent reply other threads:[~2022-10-02 5:57 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 [this message]
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
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=5E327D85-FFF2-4633-98B7-B53EC9A8038B@gmail.com \
--to=casouri@gmail.com \
--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).