Thanks for that nice addition!

If I understand correctly, eglot-jl needs to be "installed" somewhere on the remote system. But users can't do this using package managers and such, which presumably means that the easiest (the only?) way would be to clone the git repository (as you mentioned in #39). Do you think this could be mentioned in the README paragraph?

Also, do you think there could be a risk of things failing if the locally installed version of eglot-jl falls out-of-sync with the remote one? AFAIU, eglot will use e-lisp code from the locally installed eglot-jl, but the julia code used to start the LanguageServer will come from the remote system.

If I understand correctly, eglot-jl needs to be "installed" somewhere on the remote system. But users can't do this using package managers and such, which presumably means that the easiest (the only?) way would be to clone the git repository (as you mentioned in #39). Do you think this could be mentioned in the README paragraph?

Good point, I will do so.

Also, do you think there could be a risk of things failing if the locally installed version of eglot-jl falls out-of-sync with the remote one? AFAIU, eglot will use e-lisp code from the locally installed eglot-jl, but the julia code used to start the LanguageServer will come from the remote system.

Yes, that is in principle true, but eglot-jl.el does not have much code, it is basically just a convenience wrapper around eglot that sets the appropriate variables, so I don't think it is a problem in practice.

Thanks for the contribution! I haven't had time to review yet but will try to do so in the coming weeks. Something I ran across this week which might be interesting to you: it's apparently possible to run the language server on your home system while using tramp to edit something remotely.