Jason Lee
83f9f9d9e3
Release Notes: - N/A --- - Set `.SystemUIFont` as the GPUI default font. - Add `Arial` to font fallback list. - Add `Adwaita Sans` to default fallback list for Gnome. - Move `Ubuntu` font to front of Gnome to make sure Ubuntu System takes priority over `Ubuntu` font. Our application get some crash report: ``` panicked at /Users/admin/.cargo/git/checkouts/zed-a70e2ad075855582/f1db3b4/crates/gpui/src/text_system.rs:150:9: failed to resolve font 'Helvetica' or any of the fallbacks: Zed Plex Mono, Helvetica, Segoe UI, Cantarell, Ubuntu, Noto Sans, DejaVu Sans ``` This change to add `Arial` to fallback list, this font was included in macOS and Windows. Ref link (search "Arial"): > Mac OS X (now known as [macOS](https://en.wikipedia.org/wiki/MacOS)) was the first Mac OS version to include Arial; > https://en.wikipedia.org/wiki/Arial - macOS Sequoia: https://support.apple.com/en-us/120414 - Windows 10: https://learn.microsoft.com/en-us/typography/fonts/windows_10_font_list - Gnome: https://developer.gnome.org/hig/guidelines/typography.html
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.