On Sat, Apr 29, 2023, at 1:13 PM, Philip Kaludercic wrote: > Dmitry 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 , 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. > > 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.