How to update Eglot post Emacs 29

[refaelsh]

Since Eglot is now part of Emacs 29, I have several questions please:

1. How to update the built-in Eglot in Emacs 29?
2. Will (use-package eglot) continue to work as usual?
3. What will happen to Github's repo of Eglot?

[joaotavora]

How to update the built-in Eglot in Emacs 29?

The safest way is to type M-x eglot-upgrade-eglot into Emacs 29. That command also works in Emacs versions older than 29, provided that eglot.el is at least 1.16. For Eglot 1.15, the command is named eglot-update.

2. Will (use-package eglot) continue to work as usual?

Depends on what part of that command you were relying on:

• If you relied on that command to live in your configuration and be able to bootstrap an entirely new configuration (say, in a new machine you're setting up) and rev up Eglot to its latest version, than the answer is NO, it will not continue to work as usual. In Emacs 29, the command will silently complete but Eglot will stay at an ever-ageing 1.12.29 version, which is the built-in version that ships with Emacs 29.
• If you never used that command to bootstrap new systems and expect Eglot to be upgraded to latest, then you may continue to use it. In this case, you may manually use eglot-upgrade-eglot to advance the Eglot version manually to the latest available one.

The remaining parts of the use-package form, where you presumably configure certain parts of Eglot, will most likely continue to function.

3. What will happen to Github's repo of Eglot?

For the time being, nothing except what is already described in the README.md

[joaotavora]

You mean this: "From a development perspective, moving to core allows us to work on Eglot in tandem with other related packages already in Emacs, such as Flymake, ElDoc, Xref, Project."?

Yes, exactly.

Can you please tell me where? I would really much like to read it.

It's on the bug tracker, subject "Not easy at all to upgrade :core packages like Eglot". It will be a very tiring and confusing read, and the only reason I can imagine someone wanting to read it now is for the popcorn. Even though I don't agree with the conclusion, I'm glad that it's done. So I will not say any more about it.

[refaelsh]

I understand now. Thank you, @joaotavora, for your replies.

[refaelsh]

someone wanting to read it now is for the popcorn

I like popcorn!

[refaelsh]

It's on the bug tracker, subject "Not easy at all to upgrade :core packages like Eglot"

I can't find it here: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs. I tried the search box with the subject you wrote and several other keywords. Can you please help?

[joaotavora]

I like popcorn!

Yes, I figured.

Can you please help?

No.

[refaelsh]

Since Eglot is now part of Emacs 29, I have several questions please:

1. How to update the built-in Eglot in Emacs 29?

2. Will `(use-package eglot)` continue to work as usual?

3. What will happen to Github's repo of Eglot?

4. Why was it decided to make Eglot part of Emacs? Would it not be better to leave it as a package, so it can be updated easily and not wait for an Emacs update?