Eduardo de Melo Xavier
d4f6ca44bc
Release Notes: - N/A TL;DR: There was a closed issue 7 hours ago that changed ashpd version, it needed another bump. A dependency of gpui called ashpd has a fix in v0.12.1, GPUI has the 0.12 version. After forking zed and patching the gpui source to be mine with 0.12.1 it was able to use GPUI as a dependency and compile the project. The error I was getting and the recomendation to do this PR can be seen in this [closed issue from ashpd](https://github.com/bilelmoussaoui/ashpd/issues/325). After changing the dependecy I hit cargo check: ```bash Finished `dev` profile [unoptimized + debuginfo] target(s) in 4m 24s ``` And cargo run: ```bash Compiling zed v0.220.0 (/home/user/git/xaviduds/zed/crates/zed) Finished `dev` profile [unoptimized + debuginfo] target(s) in 9m 44s Running `target/debug/zed` ``` Zed compiled and opened: <img width="1920" height="1042" alt="image" src="https://github.com/user-attachments/assets/8bc524d1-bc4a-43f8-9da4-b02faecca30c" />
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 (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
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.