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
Andrei Zvonimir Crnković c77dd8b9e0
docs: Add linux build command explanation (#11513)
Just adding a short note about `cargo build --release` and the location
of the compiled binary. It helps a lot to streamline usage of Zed day to
day on Linux.

Release Notes:

- N/A
2024-05-07 14:37:34 -07:00
.cargo
.config
.github Update pull_request_template.md 2024-05-07 08:51:38 -06:00
.zed
assets Add DecoratedIcon (#11512) 2024-05-07 16:36:13 -04:00
crates Do not show diffs for files with \r\n contents (#11519) 2024-05-08 00:37:09 +03:00
docs docs: Add linux build command explanation (#11513) 2024-05-07 14:37:34 -07:00
extensions gleam: Add runnable tests (#11476) 2024-05-06 22:26:36 -04:00
script linux: Use optional compile-time RELEASE_VERSION variable (#11490) 2024-05-07 17:50:19 +02:00
tooling/xtask
.dockerignore
.gitattributes
.gitignore
.gitmodules
.mailmap
Cargo.lock assistant2: Add general structure for conversation history (#11516) 2024-05-07 17:03:33 -04:00
Cargo.toml
CODE_OF_CONDUCT.md
CONTRIBUTING.md
debug.plist
docker-compose.sql
docker-compose.yml
Dockerfile
LICENSE-AGPL
LICENSE-APACHE
LICENSE-GPL
livekit.yaml
Procfile
README.md
rust-toolchain.toml
typos.toml Restore vim docs (#11491) 2024-05-07 09:24:00 -06:00

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 using Homebrew:

brew install --cask zed

Alternatively, to install the Preview release:

brew install --cask zed@preview

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 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.