mirror of
https://github.com/zed-industries/zed.git
synced 2026-07-10 00:13:29 +00:00
On Windows, Zed generated a .ps1 askpass script and set **SSH_ASKPASS** to 'powershell.exe -ExecutionPolicy Bypass -File ...'. SSH calls exec() on SSH_ASKPASS which cannot exec a command string, causing: error: ssh_askpass: exec(powershell.exe ...): No such file or directory Fix by pointing **SSH_ASKPASS** directly to cli.exe and passing the socket path via **ZED_ASKPASS_SOCKET** env var, which cli.exe reads before clap parses arguments. --- > Compiling Zed almost blew up my computer. --- Related #29048 Release Notes: - Fixed some ssh issues on windows that prevented from connecting to a remote |
||
|---|---|---|
| .. | ||
| src | ||
| build.rs | ||
| Cargo.toml | ||
| LICENSE-GPL | ||
| README.md | ||
Cli
Testing
You can test your changes to the cli crate by first building the main zed binary:
cargo build -p zed
And then building and running the cli crate with the following parameters:
cargo run -p cli -- --zed ./target/debug/zed.exe