emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Turning c-ts-mode.el, go-ts-mode.el, csharp-ts-mode.el etc into :cor


From: Dmitry Gutov
Subject: Re: Turning c-ts-mode.el, go-ts-mode.el, csharp-ts-mode.el etc into :core packages?
Date: Wed, 8 Mar 2023 14:25:30 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1

On 08/03/2023 06:19, Yuan Fu wrote:


On Mar 7, 2023, at 7:06 AM, Dmitry Gutov <dgutov@yandex.ru> wrote:

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).

I wish package.el has something like “install last version of xxx package 
compatible with Emacs yyy”. Then we can just bump the minimum required Emacs 
version when a new Emacs release come out, and use new features. Anyway, 
checking versions to use new Emacs feature is IMO an acceptable price to pay.

Yes, unfortunately, ELPA repositories only keep one latest version.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]