yenru0/zed

0 Fork 0

Files

T

Bennet Bo Fenner 03903ea28f cli: Always open new window when cli_default_open_behavior=new_window (#59415 )

This makes sure that the behaviour of the CLI matches that of the UI.
In Zed itself we always open a new window (e.g. when clicking on Open
Project in new window in the recent projects picker), but in the CLI we
where re-using existing windows even when specifying
"cli_default_open_behavior": "new_window".
This caused confusion, so this PR ensures that we always open a new
window, even if that folder is already open. We still focus the active
window in the case where the path is a subpath of a project that is
already open.

Can be tested with

```
cd crates/cli
cargo run -- --zed ../../target/debug/zed somefolder
```

Release Notes:

- cli: Ensure `zed somefolder` always opens a new window, even when
`cli_default_open_behavior` is set to `new_window` and the project is
already open

2026-06-30 20:10:06 +00:00

src

cli: Always open new window when cli_default_open_behavior=new_window (#59415 )

2026-06-30 20:10:06 +00:00

build.rs

Fix Windows icon resource for bin zed.exe (#54738 )

2026-05-01 22:33:54 +00:00

Cargo.toml

Add shell completions for CLI (#57440 )

2026-06-22 14:57:34 +00:00

LICENSE-GPL

chore: Change AGPL-licensed crates to GPL (except for collab) (#4231 )

2024-01-24 00:26:58 +01:00

README.md

remote: Support line and column numbers for remote paths (#40410 )

2025-10-17 10:50:22 +00:00

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