Zed Improved. Aiming to improve upon Zed and make a truly delightful code editor.
https://zed.dev
a09e5d255b
## Why? Some users expressed a preference for the AnyQuotes and AnyBrackets text objects to align more closely with traditional Vim behavior, rather than the mini.ai plugin's approach. To address this, I’ve introduced two new text objects: MiniQuotes and MiniBrackets. These retain the mini.ai plugin behavior, while the updated AnyQuotes and AnyBrackets now follow the logic described in [this bug report](https://github.com/zed-industries/zed/issues/25563) and [this bug report](https://github.com/zed-industries/zed/issues/25562). ## Behavior Overview: ### AnyQuotes and AnyBrackets: These now prioritize the innermost range first (e.g., the closest quotes or brackets). If none are found, they fall back to searching the current line. This aligns with the behavior requested in the issue. ### MiniQuotes and MiniBrackets: These maintain the mini.ai plugin behavior, prioritizing the current line before expanding the search outward. ### Usage Examples: AnyQuotes: Works like ```ci', ci", ci` , ca', ca", ca` , etc.``` AnyBrackets: Works like ```ci(, ci[, ci{, ci<, ca(, ca[, ca{, ca<, etc.``` Please give these changes a try and let me know your thoughts! ### Release Notes: - vim: Add AnyQuotes, AnyBrackets, MiniQuotes and MiniBrackets text objects --------- Co-authored-by: Ben Kunkle <ben@zed.dev> |
||
|---|---|---|
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .github | ||
| .zed | ||
| assets | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .clinerules | ||
| .cursorrules | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .rules | ||
| .windsurfrules | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| Cross.toml | ||
| debug.plist | ||
| default.nix | ||
| docker-compose.sql | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE-AGPL | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| Procfile | ||
| Procfile.postgrest | ||
| README.md | ||
| renovate.json | ||
| rust-toolchain.toml | ||
| shell.nix | ||
| typos.toml | ||
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
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 specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor 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 theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.