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
Julia 849a1324f7 Fix hovering over elements nested inside their parents
Co-Authored-By: Conrad Irwin <conrad@zed.dev>
2024-01-29 13:08:40 -05:00
.cargo
.config
.github Setup Danger (#6994) 2024-01-29 11:58:24 -05:00
.zed
assets Add Haskell file type icon (#6995) 2024-01-29 11:32:35 -05:00
crates Fix hovering over elements nested inside their parents 2024-01-29 13:08:40 -05:00
docs docs: Update configuring_zed__key_bindings.md (#6974) 2024-01-29 14:08:12 +02:00
plugins
script Setup Danger (#6994) 2024-01-29 11:58:24 -05:00
.dockerignore Add serialized versions of themes (#6885) 2024-01-27 13:35:43 -05:00
.gitignore Add serialized versions of themes (#6885) 2024-01-27 13:35:43 -05:00
.gitmodules
.mailmap Sort .mailmap alphabetically (#6711) 2024-01-25 09:51:47 -05:00
Cargo.lock theme_importer: Define more colors in VsCodeTheme (#6960) 2024-01-28 21:55:40 -05:00
Cargo.toml Add PureScript LSP/Highlighting support (#6911) 2024-01-28 17:44:50 -05:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md Style crate names in CONTRIBUTING.md (#6939) 2024-01-28 11:07:37 -05:00
debug.plist
docker-compose.sql
docker-compose.yml
Dockerfile
LICENSE-AGPL
LICENSE-APACHE
LICENSE-GPL Licenses: change license fields in Cargo.toml to AGPL-3.0-or-later. (#5535) 2024-01-27 13:51:16 +01:00
Procfile
README.md Add installation instructions to README (#6870) 2024-01-27 09:54:13 -05:00
rust-toolchain.toml
typos.toml Fix typos configuration (#6877) 2024-01-27 11:03:25 -05: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:

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.