unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: arash@gnu.org, stefankangas@gmail.com, jb@jeremybryant.net,
	emacs-devel@gnu.org, monnier@iro.umontreal.ca,
	philipk@posteo.net
Subject: Re: Why not include all ELPA packages in an Emacs release?
Date: Thu, 30 May 2024 08:49:32 +0300	[thread overview]
Message-ID: <8634pzsvbn.fsf@gnu.org> (raw)
In-Reply-To: <878qzspd9j.fsf@gnu.org> (message from Tassilo Horn on Wed, 29 May 2024 22:35:36 +0200)

> From: Tassilo Horn <tsdh@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>,  Stefan Kangas <stefankangas@gmail.com>,
>   jb@jeremybryant.net,  emacs-devel@gnu.org,  monnier@iro.umontreal.ca,
>   philipk@posteo.net
> Date: Wed, 29 May 2024 22:35:36 +0200
> 
> Arash Esbati <arash@gnu.org> writes:
> 
> > If Emacs considers in-buffer completion an important feature, then I'd
> > say corfu and cape are must.  vertico and marginalia are also must in
> > my book since they offer a better experience with vertical minibuffer
> > completion.
> 
> Nice completion UIs are certainly a very important feature and I have
> the same preferences as you.  But I don't see a reason why some specific
> one has to be in core.  It has long been ivy and company, now it's
> vertico and corfu, and in 2 years the hottest bets might be something
> else.

These are valid concerns, thanks.  However, if we consider these
features important enough and add them to core, we take the
responsibility to keep them alive for years to come, even if their
original developers move on.

> I mean, it's easy to put things into core but hardly possible to remove
> them again without annoying someone.

True.  Which is why we should consider the cost of maintaining those
as part of the decision-making.

> FWIW, I'd rather move more stuff from core to ELPA and add mechanics to
> install from ELPA easily.

No one really disagrees.  The problem is how to do that in a way that
doesn't disrupt the users and the Emacs development procedures.  See
the past discussions and the conclusions we have reached (although TBH
not all of the conclusions are agreed-upon by all of us).

> > And while we're at it: There are sometimes requests for adding AUCTeX
> > to core.  Do you have an opinion about that?
> 
> One practical question is what happens with stock tex-mode.el then.
> Right now, when you install AUCTeX, it'll take over.  That would annoy
> tex-mode users, I guess.

We don't have to make AUCTeX the default if we include it.  It could
start being optional, like the various *-ts-mode's are.



  parent reply	other threads:[~2024-05-30  5:49 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  8:48 Why not include all ELPA packages in an Emacs release? Jeremy Bryant
2024-05-28 23:15 ` Stefan Kangas
2024-05-28 23:56   ` Stefan Monnier
2024-05-29  5:59   ` Philip Kaludercic
2024-05-29 11:44   ` Eli Zaretskii
2024-05-29 15:27     ` Arash Esbati
2024-05-29 15:40       ` Eli Zaretskii
2024-05-29 16:06       ` Philip Kaludercic
2024-05-29 19:33         ` Andrea Corallo
2024-05-30 19:25           ` Adding AUCTeX to core " Jeremy Bryant
2024-05-30 19:33             ` Philip Kaludercic
2024-05-31 18:58               ` Jeremy Bryant
2024-06-07 22:00                 ` Jeremy Bryant
2024-06-08  6:56                   ` Philip Kaludercic
2024-06-08  9:40                   ` Arash Esbati
2024-06-08 15:25                   ` Stefan Monnier
2024-06-08 15:49                     ` Po Lu
2024-06-09  3:54                       ` Stefan Monnier
2024-06-09 19:39                         ` Stefan Kangas
2024-05-29 22:16         ` Arash Esbati
2024-05-29 22:19           ` Dmitry Gutov
2024-05-30  6:25           ` Philip Kaludercic
2024-05-30  6:33             ` Daniel Mendler via Emacs development discussions.
2024-05-30  7:28               ` Philip Kaludercic
2024-05-30  8:15                 ` Daniel Mendler via Emacs development discussions.
2024-05-30 15:20                   ` Philip Kaludercic
2024-05-29 20:35       ` Tassilo Horn
2024-05-29 22:04         ` Arash Esbati
2024-05-30  5:51           ` Eli Zaretskii
2024-05-30 10:52             ` Arash Esbati
2024-05-30  5:49         ` Eli Zaretskii [this message]
2024-05-30  7:55         ` Po Lu
2024-05-30 11:20           ` Eli Zaretskii
2024-05-30 11:53             ` Po Lu
2024-05-30 12:19               ` Eli Zaretskii
2024-05-30 12:58                 ` Po Lu
2024-05-30 14:11                   ` Stefan Monnier
2024-05-30 14:26                     ` Po Lu
2024-05-30 13:53           ` Stefan Monnier
2024-05-30 14:05             ` Po Lu
2024-05-30 15:02               ` Stefan Monnier
2024-05-30  8:00         ` Philip Kaludercic
2024-05-29 20:44     ` Stefan Kangas
2024-05-30  5:09       ` Eli Zaretskii
2024-06-07 21:48         ` Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?] Jeremy Bryant
2024-06-08  6:14           ` Eli Zaretskii
2024-06-08  8:10             ` Michael Albinus
2024-06-08  8:38               ` Eli Zaretskii
2024-06-08 15:55                 ` Michael Albinus
2024-06-08 16:47                   ` Eli Zaretskii
2024-06-08 16:59                     ` Michael Albinus
2024-06-07 21:55       ` Candidate packages for ELPA bundling " Jeremy Bryant
2024-06-08  1:44         ` Po Lu
2024-06-08  2:11           ` Dmitry Gutov
2024-06-08  2:46             ` Po Lu
2024-06-08  6:41               ` Philip Kaludercic
2024-06-08  6:54                 ` Po Lu
2024-06-08  7:47                   ` Philip Kaludercic
2024-06-08 15:06                     ` Stefan Monnier
2024-06-08 16:24                       ` Philip Kaludercic
2024-06-08 15:09             ` Stefan Monnier
2024-06-08  6:25           ` Eli Zaretskii
2024-06-08  6:48             ` Po Lu
2024-06-08 15:18           ` Stefan Monnier
2024-06-08 15:37             ` Po Lu
2024-06-08 15:53               ` Stefan Monnier
2024-06-09  0:06                 ` Po Lu
2024-06-09  3:55                   ` Stefan Monnier
2024-06-08  6:55         ` Philip Kaludercic

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=8634pzsvbn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arash@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --cc=stefankangas@gmail.com \
    --cc=tsdh@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).