From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov 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 03:52:48 +0300 Message-ID: <4624e69a-6b29-e807-328d-e0b36259de9e@gutov.dev> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23306"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Cc: Eli Zaretskii , emacs-devel@gnu.org, joaotavora@gmail.com To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 29 02:53:46 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 1psYqP-0005tR-Ja for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Apr 2023 02:53:46 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1psYph-0003T6-2W; Fri, 28 Apr 2023 20:53:01 -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 1psYpf-0003Sv-7u for emacs-devel@gnu.org; Fri, 28 Apr 2023 20:52:59 -0400 Original-Received: from wnew4-smtp.messagingengine.com ([64.147.123.18]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1psYpc-0004dD-Sz; Fri, 28 Apr 2023 20:52:58 -0400 Original-Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.west.internal (Postfix) with ESMTP id 34C262B067EB; Fri, 28 Apr 2023 20:52:53 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 28 Apr 2023 20:52:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1682729572; x=1682733172; bh=c5KzaBcDZDD2EfY1I4ZMgv8Guj5/obCGRVq UleR6bpY=; b=IIMiCEFJK7KAkBXShny/iEUigu5BPndbCmWM1cb+tGY4r1TF+al CWBfhzc2YH4t0j4Cnp4rBQVYmBf7N+EeJkl2VLvIj0vYS88BZM6mbnUiV/hfbAn3 FyhYvKk8y0JBHy5HE9P3SI+jzskNZawUUP7KcKKqf8WOBoDWyU3qQbSmi95uOxTt QCfruf+ANFwOksIqrqeTz9s8W/wUIHyPrQTO/CKhpavXCcnUjHvZK5TplAF423Li 001LHal2Hx73oiry+57FAwcIE7ZnhyMGgAXr0UwV5wFzRbMBK/s+xDDkzADcSZrg Mj/IYzNXN+MHkNjWMT84q3HhQvWNn7NkbZQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1682729572; x=1682733172; bh=c5KzaBcDZDD2EfY1I4ZMgv8Guj5/obCGRVq UleR6bpY=; b=Jns4SYKrqC/h2RdqQU6lazrQ3TrYUCD1b1rbCUJI1+sGb3Pkzif CRrEdkAeryjUxz+yfzrei/TG1ayVkhjbL2MxvXAI2m+8s6wkKgwZ9DqCtH1hdAO/ 5qrHsY4pIzuii4Z9IJWNgzntBXCCm79GThpwpvfVC+nb8aBBaieYm6TKFn3fafYa 4FoVk3esx4KUPfvsOxBrhY3OnWqDGlIbOJVp8lK/dxcCrBO1GUlzgE6mevPa/UMK JodkfXiA/wBEKFt0tTX9fJWgRBXNp54xCwm87sL4hopaGKeWwkHscJxUMjd6QS7+ 2/+kMwxWlDvVtdKtcCxtg0hQOP379nN9rcA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeduledgfeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeffmhhi thhrhicuifhuthhovhcuoegumhhithhrhiesghhuthhovhdruggvvheqnecuggftrfgrth htvghrnhephfffheeljeffgeffueeghfekkedtfffgheejvdegjeettdduheeufffggfef jeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepug hmihhtrhihsehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 28 Apr 2023 20:52:50 -0400 (EDT) Content-Language: en-US In-Reply-To: <87jzxvg9kx.fsf@posteo.net> Received-SPF: pass client-ip=64.147.123.18; envelope-from=dmitry@gutov.dev; helo=wnew4-smtp.messagingengine.com X-Spam_score_int: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.422, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:305702 Archived-At: On 28/04/2023 21:12, Philip Kaludercic wrote: > Dmitry Gutov writes: > >> On 28/04/2023 17:25, Philip Kaludercic wrote: >>> Eli Zaretskii writes: >>> >>>>> Date: Fri, 28 Apr 2023 02:52:56 +0300 >>>>> From: Dmitry Gutov >>>>> >>>>> Hi! >>>>> >>>>> On 28/04/2023 02:39, João Távora wrote: >>>>>> * lisp/progmodes/eglot.el (eglot-update): New command. >>>>> Should it be called eglot-upgrade now as well? >>>> No, it should be removed. >>> 1+ >> >> This doesn't sound very constructive at this point. > > It is difficult to be constructive here. I believe that the long-term > complications/confusion of introducing this kind of a command instead of > instructing users on Emacs 29 to update a package like Eglot manually is > not worth it, while others do. These matters are difficult to quantify, > so we cannot reach a consensus by pointing to some objective reality, > and instead of have to fall back on personal impressions and > experiences. I have a hunch that João as the maintainer of Eglot is > over-exposed to people who are interested in having the absolutely > newest version so they can make use of the absolutely newest features, > while most people I know, personally or online, that make use of Eglot > barley bother to configure it at all (I consider that to be one of the > major setting points for the package, btw). Comparing other > configurations I have seen online, I actually think that what I have in > my init.el is a lot: > > --8<---------------cut here---------------start------------->8--- > (setup eglot > (setopt eglot-autoshutdown t > eglot-extend-to-xref t > eldoc-echo-area-use-multiline-p nil > eldoc-idle-delay 0.1) > (:bind "C-c a" #'eglot-code-actions > "C-c z" #'eglot-format > "C-c r" #'eglot-rename) > (:unbind [remap display-local-help])) > --8<---------------cut here---------------end--------------->8--- 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. The newest version of Eglot is not just the latest shiny, it's also the most recent mapping of modes to language servers, for example. Or mapping of Emacs features to LSP capabilities. And Emacs 29 will continue to be installed and used 3-5-7 years after its release, where some of this stuff will definitely get outdated. If we fixed package-upgrade, that could be easy enough, but 'M-x eglot-upgrade' can be a comparable alternative. > 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. > Even > just promoting the concept of having a package-specific upgrade command > is something I am a afraid of (it took for ages for third-party packages > to stop adding pointless `foo-version' commands). And I might have > missed something here, but none of this would tackle the "central" issue > of use-package not installing the newest version of a package if the > package is already built-in, but hasn't yet been installed before. I don't know if it's "central": according to the docs, (use-package eglot :ensure t) is only meant to ensure that Eglot is installed. Whether that means the very latest version at the time the configuration is first run, or not, seems a matter of opinion.