Richard Feldman
bfa5e88b66
Dramatically simplifies what "New Worktree" does when forking a workspace. Previously we captured the entire dock structure and all open file paths, then restored them all in the new worktree workspace. Now the behavior is: - If you have an active buffer open, we reopen just that one file (no other buffer state is carried over). - If you do not have an active buffer open, we instead fullscreen (zoom) the agent panel (equivalent to cmd-esc). No other workspace state is carried over. Implementation details: - Replace `capture_dock_state` / `set_dock_structure` / `open_item_abs_paths` with a single `active_file_path` lookup. - Pass `None` for the `init` closure instead of restoring dock layout. - Only reopen the single active file via `open_paths`, with proper error logging (`detach_and_log_err`) instead of silent `.detach()`. - Emit `PanelEvent::ZoomIn` on the agent panel when no active buffer exists, after `focus_panel` to ensure the panel is properly activated first. - Warn when an active file exists but cannot be remapped to the new worktree. Closes AI-87 Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.