From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: yandros@gmail.com, luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Hosting tree-sitter pre-built language definitions on ELPA?
Date: Mon, 03 Oct 2022 18:56:54 +0300 [thread overview]
Message-ID: <837d1gzyrd.fsf@gnu.org> (raw)
In-Reply-To: <FAC05763-2217-4BF4-9982-B19EBDE8DE4C@gmail.com> (message from Yuan Fu on Sun, 2 Oct 2022 15:17:35 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sun, 2 Oct 2022 15:17:35 -0700
> Cc: chad <yandros@gmail.com>,
> Po Lu <luangruo@yahoo.com>,
> emacs-devel@gnu.org
>
> > Yes. I don't think it's fair to expect the Emacs project to provide
> > such degree of hand-holding. It would place too much burden on our
> > insufficient resources.
> >
> > If downloading and building the tree-sitter language definitions is
> > too much for many users, I expect the Emacs distros to provide
> > prebuilt packages for that.
>
> I brought this up because someone suggested to bundle language definitions with Emacs for better access. If we decide to not provide hand-holding, I don’t mind doing less work ;-)
I think at least at first we should not make this our job. We could
revisit that decision later, based on actual experience and user
feedback, but up front I don't see why we should do this as part of
the Emacs project.
next prev parent reply other threads:[~2022-10-03 15:56 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837d1gzyrd.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.