Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Find a file
Conrad Irwin fcbc220408
Don't log errors on main (#7289)
Release Notes:

- N/A
2024-02-02 19:24:49 -07:00
.cargo
.config
.github Tweak pull request template to (hopefully) make it clearer (#7287) 2024-02-02 11:41:47 -05:00
.zed
assets vim hml (#7298) 2024-02-02 19:24:36 -07:00
crates Don't log errors on main (#7289) 2024-02-02 19:24:49 -07:00
docs Update configuring_zed__key_bindings.md (#7310) 2024-02-03 02:15:31 +02:00
plugins
script Don't log errors on main (#7289) 2024-02-02 19:24:49 -07:00
.dockerignore
.gitattributes
.gitignore
.gitmodules
.mailmap
Cargo.lock theme_importer: Make VS Code theme parsing more lenient (#7292) 2024-02-02 12:09:05 -05:00
Cargo.toml Add OCaml support (#6929) 2024-02-02 16:58:07 +02:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
debug.plist
docker-compose.sql
docker-compose.yml
Dockerfile Deploy collab like nightly (#7174) 2024-02-01 11:54:49 -07:00
LICENSE-AGPL
LICENSE-APACHE
LICENSE-GPL
Procfile
README.md
rust-toolchain.toml
typos.toml

Zed

CI

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:

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, add publish = 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 the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.