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 44ebd9cbd56 2/2: Eglot: explain how to update Eglot in manual (bug#62720) Date: Sat, 29 Apr 2023 09:45:22 +0300 Message-ID: <837ctvqj99.fsf@gnu.org> References: <168263878553.23108.4718240877999827191@vcs2.savannah.gnu.org> <20230427233949.44D31C22A13@vcs2.savannah.gnu.org> <20f53b0a-d6ff-8ec0-2f8c-e0e22b2d49dc@gutov.dev> <83bkj8sjv4.fsf@gnu.org> <87cz3oaxsq.fsf@posteo.net> <8bbac559-396d-531e-e282-ed6b319cd99b@gutov.dev> <87jzxvg9kx.fsf@posteo.net> <4624e69a-6b29-e807-328d-e0b36259de9e@gutov.dev> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28612"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, emacs-devel@gnu.org, joaotavora@gmail.com To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 29 08:45:20 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 1pseKd-0007E6-Mn for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Apr 2023 08:45:19 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pseK8-0001II-6F; Sat, 29 Apr 2023 02:44:48 -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 1pseK6-0001I4-Hc for emacs-devel@gnu.org; Sat, 29 Apr 2023 02:44:46 -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 1pseK6-00017m-1o; Sat, 29 Apr 2023 02:44:46 -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=dMX0xOkYXu40Kupm4mV1aAKu44AcJ5rJayfjwSsrYfI=; b=iiCw4QMCJ6GY Qe3c4WjriVa1O7JorYBUWCAkgicq+96PRA3BzkOtdTNl0Rbjdl4N0A3AGnXB2qnDh/tQRkcVM6xK0 twBypBck1CDs34qhPgCA8d0JgH8/RJOg6fnH9K5kTpnMrbotCP1spq3k/1fOUdJpYMQVII45FYw2b W+KFPqRvaoBL7j6+Wp/RlTtFOtNnPKFaBjkasv/nWs13Sizx2aUUQgewaSuIpRoax3PgAYSRGda4Z PyAE3RzxCfUjXThmq/UaqHyq+hZ5L155ozWblCoI+LT6xnKsnSK8j6Mf6NEqfDm5ZKpzo1ZG/Knyg REAa3LiPbdnQL0Ug9LgZsg==; 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 1pseK5-0005Mw-Dm; Sat, 29 Apr 2023 02:44:45 -0400 In-Reply-To: <4624e69a-6b29-e807-328d-e0b36259de9e@gutov.dev> (message from Dmitry Gutov on Sat, 29 Apr 2023 03:52:48 +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:305706 Archived-At: > Date: Sat, 29 Apr 2023 03:52:48 +0300 > Cc: Eli Zaretskii , emacs-devel@gnu.org, joaotavora@gmail.com > From: Dmitry Gutov > > But that's the thing: upgrading to a recent version of Eglot is not only > for the more advanced user. Those can easily go the 'M-x list-packages > C-s eglot i x' route. > > It is those who do the minimum customization and/or are just introduced > to Emacs, can miss out with more likelihood the longer the steps to > upgrade Eglot are going to be. At the risk of sounding like a broken record: introducing a new command for upgrading Eglot has the same problem as the original one: users of Emacs 29 will need to use a different procedure for upgrading Eglot than they used before. So it doesn't solve any problems, only introduces new ones. It's a mistake that should be fixed while we still can. > > Just thinking about introducing a command that we right-now plan to > > deprecate by the next release is not something I look forward to. > > It would probably be deprecated only several major versions later. It was deprecated the minute it was introduced.