-
-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyls remote over tramp not working #3391
Labels
Comments
Possibly related to this |
yyoncho
added a commit
to yyoncho/lsp-mode
that referenced
this issue
Oct 27, 2023
- This fixes the implementation of `lsp-mode` tramp support. After this PR the remote clients will be automatically registered and in most of the cases it will work out of the box. The remote connection is managed to a way similar to what eglot does. Fixes emacs-lsp#4158 Fixes emacs-lsp#4150 Fixes emacs-lsp#4158 Fixes emacs-lsp#4150 Fixes emacs-lsp#3841 Fixes emacs-lsp#3642 Fixes emacs-lsp#3579 Fixes emacs-lsp#3530 Fixes emacs-lsp#3491 Fixes emacs-lsp#3490 Fixes emacs-lsp#3391 Fixes emacs-lsp#3369 Fixes emacs-lsp#3364 Fixes emacs-lsp#3020 Fixes emacs-lsp#3018 Fixes emacs-lsp#3020
yyoncho
added a commit
to yyoncho/lsp-mode
that referenced
this issue
Oct 30, 2023
- This fixes the implementation of `lsp-mode` tramp support. After this PR the remote clients will be automatically registered and in most of the cases it will work out of the box. The remote connection is managed to a way similar to what eglot does. Fixes emacs-lsp#4158 Fixes emacs-lsp#4150 Fixes emacs-lsp#4158 Fixes emacs-lsp#4150 Fixes emacs-lsp#3841 Fixes emacs-lsp#3642 Fixes emacs-lsp#3579 Fixes emacs-lsp#3530 Fixes emacs-lsp#3491 Fixes emacs-lsp#3490 Fixes emacs-lsp#3391 Fixes emacs-lsp#3369 Fixes emacs-lsp#3364 Fixes emacs-lsp#3020 Fixes emacs-lsp#3018 Fixes emacs-lsp#3020
yyoncho
added a commit
to yyoncho/lsp-mode
that referenced
this issue
Nov 2, 2023
* Fix lsp-mode's tramp support - This fixes the implementation of `lsp-mode` tramp support. After this PR the remote clients will be automatically registered and in most of the cases it will work out of the box. The remote connection is managed to a way similar to what eglot does. Fixes emacs-lsp#4158 Fixes emacs-lsp#4150 Fixes emacs-lsp#4158 Fixes emacs-lsp#4150 Fixes emacs-lsp#3841 Fixes emacs-lsp#3642 Fixes emacs-lsp#3579 Fixes emacs-lsp#3530 Fixes emacs-lsp#3491 Fixes emacs-lsp#3490 Fixes emacs-lsp#3391 Fixes emacs-lsp#3369 Fixes emacs-lsp#3364 Fixes emacs-lsp#3020 Fixes emacs-lsp#3018 Fixes emacs-lsp#3020 * Use executable-find with remote = t everywhere
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
I am having trouble to set up pyls on a remote machine via tramp.
I've read #1845 , #2514 and #2375 but still can't get it to work.
Either (see below) due to a json issue, pyls-remote remains in 'starting' and the session, thus, has no capabilities.
Or the session starts and has capabilities but these do not return.
Steps to reproduce
For my tests I run
with this
~/.emacs.lsp.minimal
Without the dirty fix from the THIRD SUGGESTION
(#1845 (comment))
pyls-remote remains in 'starting' and
lsp-describe-session
reportsno capabilities. Additionally, this is in
tmp/pyls-remote-1-stderr
:With the dirty fix from the THIRD SUGGESTION
(#1845 (comment))
pyls-remote is successfully started and
lsp-describe-session
reportssome capabilities. Additionally,
tmp/pyls-remote-1-stderr
iscreated, but remains empty. But all of the lsp-related functions
never return (I've even removed the timeout and waited for ~15 minutes).
With the SECOND SUGGESTIONS (a and b) I get
but
(executable-find "pyls" t)
successfully finds pyls.The FIRST SUGGESTIONS does not seem to change any of this behaviour.
Expected behavior
pls-find-references to return (ideally with correct references...)
Which Language Server did you use?
pyls
OS
Linux
Error callstack
No response
Anything else?
Here is my setup.
Client:
Remote Machine:
The text was updated successfully, but these errors were encountered: