Kirill BulatovandLukas Wirth
97b429953e
An attempt to re-land https://github.com/zed-industries/zed/pull/41043 Part of https://github.com/zed-industries/zed/issues/5259 (as `>>>` forms a ligature that we need to break into differently colored tokens) Before: <img width="301" height="86" alt="image" src="https://github.com/user-attachments/assets/e710391a-b8ad-4343-8344-c86fc5cb86b6" /> and https://github.com/user-attachments/assets/ae77ba64-ca50-4b5d-9ee4-a7d46fcaeb34 After: <img width="1254" height="302" alt="image" src="https://github.com/user-attachments/assets/7fd5dba5-d798-4153-acf2-e38a1cb712ae" /> When certain combination of characters forms a ligature, it takes the color of the first character. Even though the runs are split already by color and other properties, the underlying font system merges the runs together. Attempts to modify color and other, unrelated to font size, parameters, did not help on macOS, hence a somewhat odd approach was taken: runs get interleaved font sizes: normal and "normal + a tiny bit more". This is the only option that helped splitting the ligatures, and seems to render fine. Release Notes: - Fixed ligatures forming between different text kinds --------- Co-authored-by: Lukas Wirth <lukas@zed.dev>
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.
Other platforms are not yet available:
- 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.