-
Notifications
You must be signed in to change notification settings - Fork 459
windows have not mason/packages/python-lsp-server/venv/bin/python #778
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
Closed
2 tasks done
Comments
Without the problem on my Win10,,you kan use |
我重新安装pylsp,虽然还是会显示错误,但实际是安装成功的,但是plugin还是不能安装 |
ayamir
added a commit
that referenced
this issue
Jun 1, 2023
Signed-off-by: ayamir <[email protected]>
ayamir
added a commit
that referenced
this issue
Jun 1, 2023
Signed-off-by: ayamir <[email protected]>
singlemancombat
pushed a commit
to singlemancombat/nvim-config
that referenced
this issue
Jun 1, 2023
…amir#779) Signed-off-by: ayamir <[email protected]>
csyJoy
pushed a commit
to csyJoy/nvimdots
that referenced
this issue
Jun 4, 2023
…amir#779) Signed-off-by: ayamir <[email protected]>
bleedingfight
pushed a commit
to bleedingfight/nvimdots
that referenced
this issue
Jun 22, 2023
…amir#779) Signed-off-by: ayamir <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version confirmation
Following prerequisites
Neovim version
nvim 0.9
Operating system/version
windows 10
Terminal name/version
Alacritty
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
HTTPS (use_ssh = false)
Affected language servers
python
How to reproduce the issue
windows下不能自动安装pylsp插件
Actual behavior
windows下不能自动安装pylsp插件
Expected behavior
windows下自动安装pylsp插件
我觉得是这个问题:
lsp.lua:
local venv = vim.fn.stdpath("data") .. "/mason/packages/python-lsp-server/venv"
require("plenary.job")
:new({
command = venv .. "/bin/python",
但是windows下的目录是
AppData\Local\nvim-data\mason\packages\python-lsp-server\venv\Scripts\python
如果直接修改这个,linux下又要改,有没有跨平台的做法
Support info
nothing
Logs
No response
Additional information
The text was updated successfully, but these errors were encountered: