From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-29 9b775ddc057 1/2: ; * etc/EGLOT-NEWS: Fix wording of last change. Date: Sun, 07 May 2023 13:55:28 +0300 Message-ID: <83mt2ge7hb.fsf@gnu.org> References: <168335548287.8529.4912240840977468283@vcs2.savannah.gnu.org> <20230506064443.56C75C22F15@vcs2.savannah.gnu.org> <59835735-faa0-4096-e491-35ec92964b7a@gutov.dev> <831qjthhm8.fsf@gnu.org> <715cdac6-83f6-6907-2ff8-3b33381f3487@gutov.dev> <83zg6hg29c.fsf@gnu.org> <83ttwpfvcr.fsf@gnu.org> <83h6spfose.fsf@gnu.org> <35df1362-fd92-9424-97d0-df3479414677@gutov.dev> <83edntfm6e.fsf@gnu.org> <667d5cc1-4a3c-5cd4-21c0-adff89cea769@gutov.dev> <834jopfdwz.fsf@gnu.org> <83v8h4elki.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23036"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 07 12:55:18 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pvc2w-0005oD-L6 for ged-emacs-devel@m.gmane-mx.org; Sun, 07 May 2023 12:55:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pvc2C-0004oO-Aa; Sun, 07 May 2023 06:54:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvc2A-0004mU-NA for emacs-devel@gnu.org; Sun, 07 May 2023 06:54:30 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvc2A-0002yW-Dp; Sun, 07 May 2023 06:54:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=KHAxR2ZuHCkVdaEajYCDeXqcGKIsJ57HxjK4/mBjYYk=; b=YRsCU9+MXa69 gbL/WRI3W0+ZoD3tZXST8En0z94eI1h9D1yzgJfv6z88UZsZvXdUJl+Azl1SRQxpu2p9yCFXIkvEy nHxU/N+P6WA0RHTwXko2j5CyMn+APaUEdIjqIxi0XMB88Te9DbB03RAlhJZ+1NXvcVUYDvnj8z47c josd4sa7i5ISZwjMJstpeRVwL/U8oEm3Yvx56kYmNe3LYZjx3L/q7S6KZbdBXDGf1NlyTiWQs63S2 +U9cPWr5Qn51ZQ7foEkL6b2oBd+yPUjJDYvLPCIPSBg4ylh1lzzF46HXsCKETd8W1pS4LbfSWbKft FCxle0AmAowMGW6OokhOqQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvc29-0008Fc-TQ; Sun, 07 May 2023 06:54:30 -0400 In-Reply-To: (message from Dmitry Gutov on Sun, 7 May 2023 12:50:31 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:305946 Archived-At: > Date: Sun, 7 May 2023 12:50:31 +0300 > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > From: Dmitry Gutov > > > Also, "/ u" should ideally show built-in packages as well, when > > package-install-upgrade-built-in is non-nil. > > So we think upgrading built-in packages could be dangerous, but if the > user wants to upgrade Eglot, then upgrading all built-ins is suddenly fine? It is not dangerous, it just isn't what Emacs 28 did. > If we don't actually consider upgrading of all built-ins to be a > problem, and are just hesitant to enable it in Emacs 29, then I guess it > is fine. There are arguments both ways, and situations where Emacs 28 behaved this way or the other. So optional behavior seems to strike the right balance between the opposites. > Otherwise, we've had a pretty good idea posted previously: patch where a > variable holds the list of builtins that should be upgraded automatically. I don't think this is TRT. There's nothing special about those two packages in this regard.