Thanh NguyenandBen Kunkle
83d87e37ac
Fixes #28339 ## What - Normalize cwd-relative path-like targets that include leading `..` before worktree lookup. - Update issue #28339 tests to expect `WorktreeExact` for local and remote resolution. ## Why - Prevent terminal links like `../foo/bar.txt` from creating invalid entries; resolve to the correct worktree file instead. ## How to test - `cargo test -p terminal_view issue_28339 -- --nocapture` - Manual: open a workspace, run `echo ../foo/bar.txt` from a subdir in the terminal, then cmd/ctrl-click and confirm the correct file opens. ## Risk - Low: only changes terminal path-like resolution for `..` paths; expected to match normalized behavior. ## Checklist - [x] Tests run (`cargo test -p terminal_view issue_28339 -- --nocapture`) - [x] Docs updated (not needed) - [x] Backwards compatibility considered Release Notes: - Fixed an issue where relative paths starting with `..` would not resolve correctly when clicking the link in the terminal --------- Co-authored-by: Ben Kunkle <ben.kunkle@gmail.com>
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.