Alejandro Fernández GómezandDanilo Leal
9443c930de
Tweak the `ansi.*magenta` colours so they are not confused with `ansi.*red`. This matches how "One Light" behaves, where `ansi.*magenta` uses the same purple as for keyword. This change helps distinguish anything that the terminal might use magenta for from errors, and helps make more readable the output of certain tools. For maintainers: The color for `ansi.magenta` is the same as for `syntax.keyword`. The others are modifications on that colour to taste. If you have some specific shades that need to be used please tell me, or feel free to take over the PR. Before: `jj log` and `difftastic` output <img width="863" height="592" alt="Screenshot 2025-07-31 at 19 32 11" src="https://github.com/user-attachments/assets/994b1cbd-ff64-4620-bd51-a5073fd6eb2a" /> After: <img width="862" height="558" alt="Screenshot 2025-07-31 at 19 35 33" src="https://github.com/user-attachments/assets/49dfb856-6b63-4498-8779-b8624230d6a3" /> Release Notes: - N/A --------- Co-authored-by: Danilo Leal <daniloleal09@gmail.com>
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.