mirrors/zed
1
0
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2025-02-10 12:19:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6
Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
17729 commits 555 branches 843 tags 305 MiB
Rust 92.6%
JSON-with-Comments 5.6%
Scheme 0.7%
Shell 0.4%
JavaScript 0.2%
Other 0.3%
Find a file
Kirill Bulatov bacb2a266a
Add more data into LSP header parsing error contexts (#7282) 
Follow-up of https://github.com/zed-industries/zed/pull/6929 

Release Notes:

- N/A
2024-02-02 18:04:23 +02:00
.cargo
.config
.github Add missing secret in release nightly workflow 2024-02-01 15:45:53 -08:00
.zed
assets Revert "Add YAML file type icon (#7185)" (#7286) 2024-02-02 11:02:10 -05:00
crates Add more data into LSP header parsing error contexts (#7282) 2024-02-02 18:04:23 +02:00
docs Add OCaml support (#6929) 2024-02-02 16:58:07 +02:00
plugins
script just kidding (#7241) 2024-02-01 11:57:09 -07:00
.dockerignore
.gitattributes
.gitignore
.gitmodules
.mailmap
Cargo.lock Add OCaml support (#6929) 2024-02-02 16:58:07 +02: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

README.md

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.