Lukas Lihotzki
d5b0df6efa
Based on the work on GLES support of @kvark, only two pieces were missing for usable GLES support: - https://github.com/kvark/blade/pull/125 was upstreamed 2 weeks ago and is contained in the currently referenced zed-industries/blade fork - https://github.com/kvark/blade/pull/126 was upstreamed 17 hours ago and is not contained in the zed-industries fork. As the zed-industries fork was also upstreamed in https://github.com/kvark/blade/pull/128, we can switch back to mainline blade. If you don't want to switch back to mainline blade, please integrate https://github.com/kvark/blade/pull/126 to your fork. Release Notes: - Fix GLES backend (#9581)
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew install --cask zed@preview
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.