-
-
Notifications
You must be signed in to change notification settings - Fork 123
Unable to install powershell_es #287
Comments
Do you have the latest git version of UPD: It seems you have. |
Hello! What is your |
You are using
The powershell editor services only work with powershell 7+ See this for reference. |
You are looking for |
Yeah we don't use |
Uh, I might be wrong, but I'm pretty sure about powershell es needing 7+. Lemme do some googling. Edit: I don't have access to my windows machine atm anyway, I'll revisit this tomorrow. |
No that seems correct! But it seems like OP is having issues with the installation only. We recently merged #284 which seems to have caused it |
Yeah, this article says the same.
That extension being what powershell ES was developed for. Imho, while you can rely on powershell 5.1 being present, I for myself consider it kinda deprecated. It seems to me MS is really pushing towards PS 7 |
Oh, you even said so. My bad, I'm a bit tired. Tldr; you need PS 7 |
powershell version is |
Thanks. Are you otherwise able to run the |
While your reasoning behind using powershell makes sense, I am pretty sure that anyone developing under windows today have pwsh and windows terminal installed. |
The command |
Does |
Yes it does. |
Oh no. I was hoping you'd get an error 😆. I really don't know what's happening here :/. Can you think of anything obvious? Here's the callsite |
It seems it does. If I start powershell and run PS. I found the problem. It was a missing PATH from my System Environment Variables. In case anyone has the same problem and search for it, the path that was missing is: |
Thank you for your time and sorry for wasting it with a problem that ended up being on my system. |
The servers appear to install correctly but I only see empty folders. It happens for sumneko_lua, omnisharp and powershell_es.
If you want me to try anything let me know. I can't think of anything else, I'll be making the change to "pwsh" locally. |
@petrosAth could you try the branch Could you then provide:
|
branch LspInstallInfo:
|
Could you pull the latest commit from that branch and try again? Does it fail at an earlier stage now? |
branch LspInstallInfo:
|
Wait so that sounds like it's working now!? |
branch Yes it does! They all install correctly now(sumneko_lua, omnisharp and powershell_es). |
Describe the bug
I have exactly the same issue with powershell_es failling to Expand-Archive.
It installs correctly if I swap "powershell.exe" with "pwsh"
Screenshots
System info (please complete the following information):
Please also include any other system information you think is relevant!
Install log
If applicable, include nvim-lsp-installer's logs. See :help nvim-lsp-installer-debugging for instructions on how to set the log level and access the logs.
The text was updated successfully, but these errors were encountered: