unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Yuan Fu <casouri@gmail.com>, Emacs developers <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 17:06:28 +0200	[thread overview]
Message-ID: <68a6b078-f91a-d392-f37f-53a86b76465b@yandex.ru> (raw)
In-Reply-To: <A2C7A2B7-7ECD-47B2-A792-84F122D3BCD0@gmail.com>

On 06/03/2023 00:41, Yuan Fu wrote:
> 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.

Most of the associated overhead is having to keep in mind the version of 
Emacs that each packages advertises compatibility with. Which makes 
using new features (or fixes) from future Emacs versions harder 
(requiring versions checks, etc).

We could also make treesit.el into a :core package at some point, if any 
of the packages will need some new changes. Although this one will 
likely depend on changes in treesit.c even more often. But for this 
package, at least, it might be worth it to set the "Version:" header in 
advance.



  parent reply	other threads:[~2023-03-07 15:06 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
2023-03-07 15:06 ` Dmitry Gutov [this message]
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

  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=68a6b078-f91a-d392-f37f-53a86b76465b@yandex.ru \
    --to=dgutov@yandex.ru \
    --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).