Add ability to change shell executor for language servers/internal processes #10233
Replies: 3 comments
-
There is no shell used, the server is started directly as a subprocess. |
Beta Was this translation helpful? Give feedback.
-
Should we then consider this a bug? At least in my eyes this is a valid use case and it's not working as expected. |
Beta Was this translation helpful? Give feedback.
-
Is Helix built for Windows on your machine? I'm not very familiar with Windows or WSL but we may not be able to call a WSL program from a Windows program in the same way that command prompt / PowerShell can't execute erlang-ls. FWIW the code to execute the language server as a child process is here: Lines 59 to 67 in bdeefbf |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Trying to set up
erlang-ls
on Windows, I compiled it and generated the required binary, which I placed in myPATH
. Running it in bash works properly. However, trying to execute the binary from the command prompt or PowerShell results in a "not a proper executable" error.Curiously, the
which
rust crate will not find an extensionless executable in thePATH
despite the fact that runningwhich erlang-ls
properly finds the file.This can be "fixed" by adding an
.exe
extension manually but when opening an erlang file, the language server fails to start, and the log shows the following line:My proposal is to make the shell executor configurable for internal processes, such as running the language servers, something akin to the
editor.shell
property. Maybe I'm going about this the wrong way but so far I haven't been able to find a workaround for runningerlang-ls
on Windows in helix.Beta Was this translation helpful? Give feedback.
All reactions