emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs-29 44ebd9cbd56 2/2: Eglot: explain how to update Eglot in manu


From: Dmitry
Subject: Re: emacs-29 44ebd9cbd56 2/2: Eglot: explain how to update Eglot in manual (bug#62720)
Date: Sat, 29 Apr 2023 14:51:02 +0300
User-agent: Cyrus-JMAP/3.9.0-alpha0-374-g72c94f7a42-fm-20230417.001-g72c94f7a



On Sat, Apr 29, 2023, at 1:13 PM, Philip Kaludercic wrote:
Dmitry <dmitry@gutov.dev> writes:

> On Sat, Apr 29, 2023, at 9:45 AM, Eli Zaretskii wrote:
>> > Date: Sat, 29 Apr 2023 03:52:48 +0300
>> > Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.orgjoaotavora@gmail.com
>> > From: Dmitry Gutov <dmitry@gutov.dev>
>> > 
>> > 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.
> But users of Emacs 28- would be able to use it too. So at least the docs could list just one method.

But they don't need it, because package-install does the right thing to
begin with?

By default, package-install indeed "does the tight thing". But it doesn't upgrade the already-installed package.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]