18fcdf1d2c
Fixes a few problems, - Uses `Boundary::Grid` instead of `Boundary::Cursor` for highlighted range adjustments. This fixes quite a few wierd behaviors around highlighting paths that had to be scrolled into view (i.e. were in the terminal history) including the issue described in the release notes as well as a regression caused by #26401 where the highlight range would span from the start of the path to the cursor location in the shell prompt - Strips all trailing `:`s from the paths, updating the highlighted range accordingly. This worked fine before and is just a visual improvement. Release Notes: - Fixed an issue where file paths in the terminal surrounded by `()` or `[]` would not be highlighted properly
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
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.