You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You may also try reproduce the issue using clean environment using the following command: M-x lsp-start-plain
Bug description
Lsp does not work over tramp when direct-async-process is used in tramp 2.7.1. I tested this with the jedi-tramp server. calling lsp will have a delay and then the minibuffer will prompt
Server jedi-tramp:50133/starting exited (check corresponding stderr buffer for details). Do you want to restart it? (y or n) n
Restarting it just leads to a loop where it exits again. The *jedi-tramp:stderr* has this message:
Process jedi-tramp stderr<1> finished
Process jedi-tramp stderr finished
I was able to work around the issue by disabling the direct aysnc processes using cl-letf when launching the server here.
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
Lsp does not work over tramp when direct-async-process is used in tramp
2.7.1
. I tested this with the jedi-tramp server. callinglsp
will have a delay and then the minibuffer will promptRestarting it just leads to a loop where it exits again. The
*jedi-tramp:stderr*
has this message:I was able to work around the issue by disabling the direct aysnc processes using
cl-letf
when launching the server here.Steps to reproduce
Enable direct async process:
Try to connect to a LSP client via TRAMP and it will terminate with an error.
Expected behavior
LSP should work over tramp.
Which Language Server did you use?
lsp-jedi
OS
MacOS
Error callstack
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: