From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Turning c-ts-mode.el, go-ts-mode.el, csharp-ts-mode.el etc into :core packages?
Date: Tue, 7 Mar 2023 20:12:17 -0800 [thread overview]
Message-ID: <54BE0EA7-58B6-4018-BF9D-183A130E3153@gmail.com> (raw)
In-Reply-To: <83zg8o66nb.fsf@gnu.org>
> On Mar 7, 2023, at 5:19 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sun, 5 Mar 2023 14:41:17 -0800
>>
>> What are the implications of turning something into a :core package? I can’t find much description of it. If my understanding of it is correct, I think it would be beneficial to make new tree-sitter modes into :core packages. Right now they are pretty bare-bones, and haven’t been “battle-tested”. Making them core packages would allow us gradually improve them and fix errors that come up. Those files I mentioned in the subject are new files, if that matters. But I don’t know if there are any downsides of turning something into a :core package.
>>
>> The new tree-sitter related files we have are:
>> - c-ts-mode.el
>> - java-ts-mode.el
>> - rust-ts-mode.el
>> - go-ts-mode.el
>> - dockerfile-ts-mode.el
>> - cmake-ts-mode.el
>> - yaml-ts-mode.el
>> - typescript-ts-mode.el
>> - ruby-ts-mode.el
>> - toml-ts-mode.el
>>
>> And we have a few “combined” files:
>> - python.el (already a :core package)
>> - js.el
>> - sh-script.el
>
> Isn't :core only relevant for ELPA packages and not for something that
> is bundled with Emacs?
I think bundled packages can become :core packages too, like eldoc.el did.
Yuan
next prev parent reply other threads:[~2023-03-08 4:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 22:41 Turning c-ts-mode.el, go-ts-mode.el, csharp-ts-mode.el etc into :core packages? Yuan Fu
2023-03-07 11:18 ` Holger Schurig
2023-03-07 13:20 ` Eli Zaretskii
2023-03-07 13:19 ` Eli Zaretskii
2023-03-08 4:12 ` Yuan Fu [this message]
2023-03-07 15:06 ` Dmitry Gutov
2023-03-08 4:19 ` Yuan Fu
2023-03-08 12:25 ` Dmitry Gutov
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=54BE0EA7-58B6-4018-BF9D-183A130E3153@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--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 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.