From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>, Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 44ebd9cbd56 2/2: Eglot: explain how to update Eglot in manual (bug#62720)
Date: Sat, 29 Apr 2023 13:52:39 +0100 [thread overview]
Message-ID: <87ildeu9yg.fsf@gmail.com> (raw)
In-Reply-To: <4624e69a-6b29-e807-328d-e0b36259de9e@gutov.dev> (Dmitry Gutov's message of "Sat, 29 Apr 2023 03:52:48 +0300")
[ I think everything has already been said in this discussion, so let me
try to answer two-in-one mails to minimize chatter. ]
PK> experiences. I have a hunch that João as the maintainer of Eglot is
PK> over-exposed to people who are interested in having the absolutely
PK> newest version so they can make use of the absolutely newest
PK> features,
I don't know what that means. I am exposed to the users I am exposed
to, and there seem to be a lot of them. A lot of reports and
conversations over here and over at GitHub. I spend my time with them,
very often having to guess things. If I can at least minimize the time
wasted agreeing on what Eglot version is being used or how to get the
newest bugfix/feature, I do want that.
PK> I have in my init.el is a lot:
PK> eldoc-echo-area-use-multiline-p nil
If you upgrade Eglot, you probably won't need this customization ;-)
DG> some of this stuff will definitely get outdated. If we fixed
DG> package-upgrade, that could be easy enough, but 'M-x eglot-upgrade'
DG> can be a comparable alternative.
PK>> Just thinking about introducing a command that we right-now plan to
PK>> deprecate by the next release is not something I look forward to.
DG> It would probably be deprecated only several major versions later.
Dmitry is right.
An interesting direction would be to fix package-upgrade in Emacs 29 &
make package.el a self-updating :core package itself. But the former
has been ruled out and the latter is also looking murky. Are there
other more complicated ways to achieve this? Of course, and
list-packages was the first workaround listed by me when I opened
bug#62720. But the menu is fraught with its own problems (slow,
complicated and sometimes downright broken by some accounts).
eglot-update _not_ the prettiest option, but it's the best _possible_
option which guarantees consistency across Emacs versions. I've
exhausted my attempts to steer this discussion in other directions.
So eglot-update it is. I buy the consistency argument, I do, but there
are plenty of <package>-version and <package>-bug too in the Emacs tree
There is even tramp-recompile-elpa. None of this is deprecated. Which
just means maintainters need things to work foremost before wanting them
to be pretty.
João
next prev parent reply other threads:[~2023-04-29 12:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168263878553.23108.4718240877999827191@vcs2.savannah.gnu.org>
[not found] ` <20230427233949.44D31C22A13@vcs2.savannah.gnu.org>
2023-04-27 23:52 ` emacs-29 44ebd9cbd56 2/2: Eglot: explain how to update Eglot in manual (bug#62720) Dmitry Gutov
2023-04-28 0:35 ` João Távora
2023-04-28 0:40 ` Dmitry Gutov
2023-05-03 22:48 ` Dmitry Gutov
2023-05-03 23:31 ` João Távora
2023-05-03 23:39 ` Dmitry Gutov
2023-05-04 0:50 ` João Távora
2023-05-04 0:56 ` Dmitry
2023-05-04 1:09 ` João Távora
2023-05-04 9:05 ` Dmitry Gutov
2023-05-05 14:01 ` João Távora
2023-05-05 15:06 ` Dmitry Gutov
2023-04-28 4:37 ` Eli Zaretskii
2023-04-28 14:25 ` Philip Kaludercic
2023-04-28 15:30 ` Dmitry Gutov
2023-04-28 18:12 ` Philip Kaludercic
2023-04-29 0:52 ` Dmitry Gutov
2023-04-29 6:45 ` Eli Zaretskii
2023-04-29 10:01 ` Dmitry
2023-04-29 10:13 ` Philip Kaludercic
2023-04-29 11:51 ` Dmitry
2023-04-29 10:34 ` Eli Zaretskii
2023-04-29 9:08 ` Philip Kaludercic
2023-04-29 9:40 ` Eli Zaretskii
2023-04-29 9:54 ` Dmitry
2023-04-29 10:15 ` Philip Kaludercic
2023-04-29 12:52 ` João Távora [this message]
2023-04-29 13:10 ` Po Lu
2023-04-30 12:12 ` Philip Kaludercic
2023-04-30 17:43 ` Michael Albinus
2023-05-01 2:09 ` João Távora
2023-05-01 7:34 ` Philip Kaludercic
2023-05-02 7:56 ` Robert Pluim
2023-05-05 5:13 ` Philip Kaludercic
2023-05-05 6:23 ` Robert Pluim
2023-05-02 20:35 ` João Távora
2023-04-29 6:42 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ildeu9yg.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.