-
Notifications
You must be signed in to change notification settings - Fork 19
Warn if coder-cli is not in PATH on Windows #357
Conversation
|
What's blocking this? Seems like it could be important for the |
|
@kylecarbs The package I'm using to check if the binary is in path seems to fail when cross-compiled for Windows from within my workspace, but works when I build on my Windows machine. I may just write my own function that does the same thing. |
5fa9eff to
3746bf5
Compare
|
It works when I remove |
| `Host coder.%s | ||
| HostName coder.%s | ||
| ProxyCommand %s tunnel %s 12213 stdio | ||
| ProxyCommand "%s" tunnel %s 12213 stdio |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do the quotes work on Linux too? I thought I tried it before...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works on windows, mac and linux from my testing.
|
This pull request has been linked to Clubhouse Story #15394: bug: escape path to coder-cli in .ssh/config. |
In Powershell and VS Code, the OpenSSH for Windows
ProxyCommandis expected to be a binary name likecoderor a Windows-like path such asC:\path\to\coder.exe.In Msys2 and Git Bash, the Linux-y OpenSSH expects the
ProxyCommandto be a binary name or a Unix-like path such as/c/path/to/coder.To support both environments simultaneously, the
ProxyCommandmust be set tocoder(or whatever binary name coder-cli has), and we must warn the user if the binary is not in$PATH.[CH-15394]