pylsp-tramp connected successfully, but no completion or checking #4314
Replies: 1 comment · 4 replies
-
It is hard to tell with that much information. Are other features working? |
Beta Was this translation helpful? Give feedback.
All reactions
-
No, it turns out
Here is my config for lsp-mode, although I don't think they are relevant. I've also tried lsp-mode for R, which works great both locally and remotely. So I think this should be an issue with pylsp-tramp... (setq lsp-auto-guess-root t
lsp-keep-workspace-alive nil
lsp-keymap-prefix nil
;; modeline
lsp-modeline-code-actions-enable nil
lsp-modeline-diagnostics-enable nil
lsp-modeline-workspace-status-enable nil
lsp-headerline-breadcrumb-enable nil
;; doc
lsp-eldoc-enable-hover nil
lsp-signature-auto-activate nil
lsp-signature-render-documentation nil
;; others
lsp-enable-folding nil
lsp-completion-provider :none
lsp-enable-indentation nil
lsp-enable-on-type-formatting nil
lsp-diagnostics-disabled-modes '(markdown-mode gfm-mode)
lsp-enable-file-watchers nil
lsp-enable-text-document-color nil) |
Beta Was this translation helpful? Give feedback.
All reactions
-
I forgot to mention that I also tried eglot with pylsp on tramp, and it works out of box. So, I think my pylsp is properly configured on my server. |
Beta Was this translation helpful? Give feedback.
All reactions
-
When you enable the logging what do you see? lsp-toggle-trace-io + lsp-workspace-show-log |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thank you for your time to answer. This is what I observe in
|
Beta Was this translation helpful? Give feedback.
-
pylsp
works very well locally. However, on a remote server, although it can be connected successfully, there is no completion or checking available, and thestderr
buffer is empty. Surprisingly, after installlsp-pyright
, bothpyright
andpylsp
work again remotely...I wonder if there is any essential config from
lsp-pyright
that is missing inlsp-mode
?Beta Was this translation helpful? Give feedback.
All reactions