Jake Nelson
fd7b2866c5
## Summary - Add a regression test covering reopening an already-open remote workspace root inside the reused workspace path - Use the resolved worktree entry instead of the local filesystem when `Workspace::open_paths` decides whether a reused path is a directory - This fixes the follow-on case where reopening an already-open SSH workspace root could show `Error: opening project path ...` because the remote root was being treated like a local file open I kept this fix in `Workspace::open_paths` rather than adding another remote-specific branch higher up, because the bug was specifically in the generic reused-workspace directory check. ## Testing - `cargo test -p recent_projects test_reopen_existing_remote_root_treats_root_as_directory -- --nocapture` - `cargo test -p recent_projects test_reuse_existing_remote_workspace_window_with_tilde_path -- --nocapture` - `cargo test -p recent_projects test_reuse_existing_remote_workspace_window -- --nocapture` Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] Tests cover the new/changed behaviour - [x] Performance impact has been considered and is acceptable Related to #30829 Release Notes: - Fixed reopening an already-open SSH workspace root showing an `opening project path` error instead of treating the root as a directory
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 discussion)
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
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
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.