yenru0/zed

0 Fork 0

Files

T

Eric Holk a104d4c979 cli: Defer app activation until after open-behavior prompt (#53915 )

On macOS, the CLI uses `LSOpenFromURLSpec` to deliver the `zed-cli://`
URL to the running Zed app. With `kLSLaunchDefaults`, Launch Services
activates (brings to foreground) the Zed app as a side effect of URL
delivery. This happens before the IPC handshake completes and before the
user can answer the terminal prompt asking whether to open in a new
window or existing workspace, forcing them to manually switch back to
the terminal.

## Fix

**CLI side** (`crates/cli/src/main.rs`): Add `kLSLaunchDontSwitch` to
the launch flags so macOS delivers the URL without activating the app.

**App side** (`crates/zed/src/zed/open_listener.rs`): Add
`cx.activate(true)` in `handle_cli_connection` after the prompt resolves
(or immediately for the URL-only path), so the app comes to the
foreground at the right time.

Linux and Windows are unaffected — they use Unix sockets and named pipes
respectively, which don't have activation side effects.

Release Notes:

- Fixed the Zed CLI activating the app window before the user answers
the open-behavior prompt in the terminal.

2026-04-14 16:56:03 +00:00

src

cli: Defer app activation until after open-behavior prompt (#53915 )

2026-04-14 16:56:03 +00:00

build.rs

releases: Add build number to Nightly builds (#42990 )

2025-11-24 13:34:04 +01:00

Cargo.toml

cli: Add first-run prompt for default open behavior and abstract IPC transport (#53663 )

2026-04-10 21:37:43 -07: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