unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: master fb061cd 1/4: ; * etc/NEWS: Rearrange and fix wording of some entries.
Date: Mon, 06 Sep 2021 21:46:12 +0300	[thread overview]
Message-ID: <83fsuhr18r.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk3AktJ9WWjK7eoH1fc=vVp2--qLay18uV1MNT+nKSHfg@mail.gmail.com> (message from Stefan Kangas on Mon, 6 Sep 2021 20:33:36 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Mon, 6 Sep 2021 20:33:36 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >  * Changes in Emacs 28.1
> >
> > -** The new NonGNU ELPA archive is enabled by default alongside GNU ELPA.
> [...]
> >  * Changes in Specialized Modes and Packages in Emacs 28.1
> [...]
> >  ** Package
> >
> > +*** The new NonGNU ELPA archive is enabled by default alongside GNU ELPA.
> > +Thus, packages on nonGNU ELPA will appear by default in the list shown
> > +by 'list-packages'.
> 
> I strongly disagree with this change, for two important reasons:
> 
> 1. This is not a change only in a specialized mode and package, but in
> a very important Emacs default.  The overwhelming majority of our
> enthusiast user-base, and likely a large proportion of our user-base,
> are using packages every day.  In fact, many users couldn't imagine
> using Emacs without them.  It's a mistake if we treat this as some
> sort of specialized concern.
> 
> 2. This is one of the more significant changes in this release, and
> deserves its place in the spotlight.  I personally put it up there
> together with native-comp as one of the things that really stand out
> in this release, and that I believe many will be excited and happy to
> hear about.

I agree with all that you say (except the string disagreement ;-), but
users will be oblivious to that change, unless the install packages
from ELPA.  The original entry, as stand-alone text, doesn't have any
practical impact on users that don't install packages, and would just
leave them wondering what is all this about.

IOW, the changed default doesn't affect anyone who doesn't use
package.el.  Which is why I moved it under that section.



  reply	other threads:[~2021-09-06 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210906101353.11322.30746@vcs0.savannah.gnu.org>
     [not found] ` <20210906101355.082C520A0A@vcs0.savannah.gnu.org>
2021-09-06 18:33   ` master fb061cd 1/4: ; * etc/NEWS: Rearrange and fix wording of some entries Stefan Kangas
2021-09-06 18:46     ` Eli Zaretskii [this message]
2021-09-06 18:49       ` Eli Zaretskii
2021-09-08 16:06       ` Stefan Kangas
2021-09-08 16:29         ` Eli Zaretskii
2021-09-08 15:26     ` Amin Bandali
2021-09-08 15:58       ` Eli Zaretskii

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=83fsuhr18r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefan@marxist.se \
    /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).