-
-
Notifications
You must be signed in to change notification settings - Fork 896
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
lsp-fsharp: failure when installing client #3022
Labels
Comments
On linux, at least, there is also an issue that the server installed had no permissions on the files (probably due to faulty .zip archive or unzip params?) -- I need to do |
Fixed now |
Hello, |
Horrih
added a commit
to Horrih/lsp-mode
that referenced
this issue
Jun 9, 2024
It caused issues on windows if unzip was found on the PATH
Horrih
added a commit
to Horrih/lsp-mode
that referenced
this issue
Jun 9, 2024
It caused issues on windows if unzip was found on the PATH
Horrih
added a commit
to Horrih/lsp-mode
that referenced
this issue
Jun 10, 2024
It caused issues on windows if unzip was found on the PATH
Horrih
added a commit
to Horrih/lsp-mode
that referenced
this issue
Jun 10, 2024
It caused issues on windows if unzip was found on the PATH
jcs090218
added a commit
that referenced
this issue
Sep 30, 2024
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.where
lsp-start-plain.el
can be downloaded here.Bug description
On a Windows system that has an
unzip
command in the PATH, the fsautocomplete client doesn't install properly.Steps to reproduce
On Windows:
unzip.exe
somewhere in thePATH
.Expected behavior
fsautocomplete installs properly.
Which Language Server did you use?
lsp-fsharp
OS
Windows
Error callstack
Anything else?
The problem is that when
unzip
is present, the install function assumes that it's on a Unix system and runs a command intended forsh
; but on Windows, it is misinterpreted bycmd
. A possible fix would be to switch the conditions here to usepowershell
in priority if present:lsp-mode/clients/lsp-fsharp.el
Lines 212 to 214 in b4e5145
The text was updated successfully, but these errors were encountered: