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
Paul Eguisier 8a659b0c60
Implement Indent & Outdent as operators (#12430)
Release Notes:

- Fixes [#9697](https://github.com/zed-industries/zed/issues/9697).

Implements `>` and `<` with motions and text objects.
Works with repeat action `.`
2024-06-04 15:17:01 -06:00
.cargo
.cloudflare
.config
.github Force 60 minutes timeout for all regular CI jobs (#12486) 2024-05-30 18:17:03 +03:00
.zed
assets Implement Indent & Outdent as operators (#12430) 2024-06-04 15:17:01 -06:00
crates Implement Indent & Outdent as operators (#12430) 2024-06-04 15:17:01 -06:00
docs Change on remote setup and one more SSH command as example (#12591) 2024-06-03 11:34:09 +03:00
extensions vue: Improve syntax highlighting (#11482) 2024-06-04 14:04:54 -07:00
script
tooling/xtask
.dockerignore
.gitattributes
.gitignore
.mailmap
Cargo.lock Make HTML to Markdown conversion more pluggable (#12653) 2024-06-04 16:14:26 -04:00
Cargo.toml Make HTML to Markdown conversion more pluggable (#12653) 2024-06-04 16:14:26 -04:00
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

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.