Zed Improved. Aiming to improve upon Zed and make a truly delightful code editor.
https://zed.dev
![]() This should eliminate a pretty significant (multiple seconds) slowdown that new users (or users after restarting their OS) have been experiencing. Previously, we would just notarize the application, which meant that every user of the application had to perform an integrity check against Apple's servers to ensure the app wasn't malicious. With this commit, we are now using `xcrun stapler staple`, which attaches the notarization ticket to both the app bundle as well as the DMG. This should prevent users from needing to reach out to Apple's notarization service in order to verify the app's integrity. You can confirm the quarantine status of the application by running `ls -l@` in `Terminal.app`: ls -l@ /Applications/Zed.app/Contents/MacOS/zed Release Notes: - Improved startup time when opening Zed for the first time or after restarting the operating system. Co-authored-by: Thorsten <thorsten@zed.dev> Co-authored-by: bennetbo <bennetbo@gmx.de> Co-authored-by: Martin Palma <m@palma.bz> Co-authored-by: evrsen <146845123+evrsen@users.noreply.github.com> |
||
---|---|---|
.cargo | ||
.config | ||
.github | ||
.zed | ||
assets | ||
crates | ||
docs | ||
plugins | ||
script | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.mailmap | ||
Cargo.lock | ||
Cargo.toml | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
debug.plist | ||
docker-compose.sql | ||
docker-compose.yml | ||
Dockerfile | ||
LICENSE-AGPL | ||
LICENSE-APACHE | ||
LICENSE-GPL | ||
Procfile | ||
README.md | ||
rust-toolchain.toml | ||
typos.toml |
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 from Homebrew:
brew install zed
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
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 specified
error for a crate you've created? If so, addpublish = false
under[package]
in your crate's Cargo.toml. - Is the error
failed to satisfy license requirements
for 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 theaccepted
array inscript/licenses/zed-licenses.toml
. - Is
cargo-about
unable 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.