shutdown all servers before starting a new one

[lolbinarycat]

My laptop doesn't have much ram, and while it can just about run one language server, if i ever start 2-3 lang servers, it will potentially lead to emacs getting oom killed.

I found eglot-shutdown-all, but I can't find a hook that is run before starting up a new lang server. eglot-mode-hook also doesn't seem to exist.

EDIT: eglot-server-initialized-hook is the correct hook. eglot-connect-hook will not work!

[joaotavora]

eglot-connect-hook maybe

…

On Sat, Oct 5, 2024, 19:08 lolbinarycat ***@***.***> wrote: My laptop doesn't have much ram, and while it can just about run one language server, if i ever start 2-3 lang servers, it will potentially lead to emacs getting oom killed. I found eglot-shutdown-all, but I can't find a hook that is run before starting up a new lang server. eglot-mode-hook also doesn't seem to exist. — Reply to this email directly, view it on GitHub <#1452>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC6PQ6V77Y3UH57MKGMYPTZ2ATK7AVCNFSM6AAAAABPNRLWL2VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGI4DAMRVHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[joaotavora]

so sorry you had such a bad ux solving your problem with my advice. I'll be sure to abstain from helping you in the future

[lolbinarycat]

I found eglot-connect-hook on my own, read the doc comment that says it is "run after connecting". that seems to pretty unambiguously say that it is not the right hook for my usecase. but somehow i'm wrong, actually, and "before" actually means "after".

i then tried your suggestion, and it didn't work.

i then read the function signature of other connection hooks, and reverse engineered the problem from there.

i have half a mind to submit a PR with a more helpful doc comment, but now i'm not sure, since you don't seem to appreciate constructive criticism.

[joaotavora]

but somehow i'm wrong, actually, and "before" actually means "after".

What are you on about? eglot-connect-hook's doc says it is run "after" connecting. And that's what it does, period. The only thing missing there is a note that it takes the server just connected to as a hook argument. If you shut down other servers using eglot-shutdown in that hook, it does what you want I think.

And possibly eglot-server-initialized-hook also works. And that hook's docstring is accurate.

i then tried your suggestion, and it didn't work.

Then why on earth did you say it did after I asked you? What relevance is that comment about "weirdly takes an argument"? It's not weird at all.

Anyway, your rather bizarre use case is probably solved easier by not using eglot-ensure (since you're such a doc and ux buff you have read the docs about that) or just remembering to to shutdown before starting M-x eglot.

[lolbinarycat]

my point was it didn't work initially, only after i did other stuff.

i think the old issue about the pre-connect hook should be revived.

[joaotavora]

There is already a pre-connect hook.

[joaotavora]

Don't use eglot-ensure. Shutdown existing servers before starting new ones.

[lolbinarycat]

i'm already not using eglot-ensure.

this isn't an answer, this is just repeating my question.

[joaotavora]

If you're not using eglot-ensure you're using M-x eglot. If this breaks down after 3 servers just you n have to learn to count to 3.

Or make some M-x lolglot command that shuts things down and then calls eglot interactively. 0 reverse engineering there.