Jakub Charvat
7c1405db37
In the gutter, it seems more intuitive to me for the unstaged hunks to be hollow, indicating an action left to complete, and the staged hunks to be filled. I therefore flipped the style of expanded hunks to match the gutter icons. Is that acceptable? And would it be a breaking change? If it is not acceptable, then 058dc216d5a284033eebd38d28853f69aa336a55 contains the opposite behaviour, it is not a problem to revert to it. In the following images, the first hunk is always ~unstaged~ staged and the second is ~staged~ unstaged. <img width="138" alt="image" src="https://github.com/user-attachments/assets/35927069-da90-424a-8988-a4eb984d865f" /> <img width="133" alt="image" src="https://github.com/user-attachments/assets/4edd0e0d-a2b5-453a-8172-47684e065c82" /> <br /> <img width="143" alt="image" src="https://github.com/user-attachments/assets/2f295944-81aa-45f3-a103-c13b92bc2aba" /> <img width="133" alt="image" src="https://github.com/user-attachments/assets/35248218-7104-4059-8742-ae0e54da6c6b" /> Release Notes: - Improved gutter diff hunks to show whether a hunk is staged
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.