Joseph T. Lyons
a9eb480f3c
The feedback modal did not match our keyboard-driven design. We can revisit this later if we want, but for now, removing it makes sense. All actions have been inlined in the `Help` menu to maintain discoverability. Additionally, not all feedback-based actions in the command palette were namespaced under `feedback:`, and now they are, so they can all be found there easily. Release Notes: - Notice: The `Give Feedback` modal has been removed. The options to file bug reports, feature requests, email us, and open the Zed repository can now be found within the `Help` menu directly. The command palette actions have undergone the following changes: - `feedback: give feedback` (removed) - `feedback: file bug report` (no change) - `zed: request feature` → `feedback: request feature` - `zed: email zed` → `feedback: email zed` - `zed: open zed repo` → `contribute: open zed repo`
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.