mirror of
https://github.com/zed-industries/zed.git
synced 2026-05-31 13:09:47 +00:00
original uri https://github.com/zed-industries/zed
https://zed.dev
011113ea3c
Follow-up to https://github.com/zed-industries/zed/pull/46641. In the PR linked above, I had introduced a dropdown that'd show up in the title bar when the workspace contained more than one project. Although that helped improve the multi-project use case, it created some quirky designs: - The project dropdown and the recent project pickers looked too different from one another - The transition between the 2 project case to the 1 project scenario, from the dropdown, was not great, because you'd be then seeing the bigger recent projects picker - The `workspace: switch project` action was still reachable in the command palette even if you had one project in the workspace So, what this PR does is essentially fixing all of this by consolidating it all in the Recent Projects picker. If you are in a multi-project scenario, the picker will display a section with all of the projects on the workspace allowing you to activate each one of them. The picker also looks simpler when you reach it by clicking on the project name in the title bar, as opposed to through the keybinding. I've then removed the project dropdown code as well as the action, given we don't need them anymore due to the consolidation. Lastly, I tackled the inconsistent wording used between "Folders", "Projects", and "Workspaces". Here's the result: https://github.com/user-attachments/assets/9d8ef3e3-e57b-4558-9bc0-dcc401dec469 - [x] Code Reviewed - [x] Manual QA Release Notes: - Workspace: Improved the recent projects picker by making it also display active projects in case of a multi-project workspace. |
||
|---|---|---|
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory/prompts/docs-automation | ||
| .github | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| debug.plist | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-AGPL | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| Procfile | ||
| Procfile.all | ||
| Procfile.web | ||
| README.md | ||
| renovate.json | ||
| REVIEWERS.conl | ||
| rust-toolchain.toml | ||
| rustfmt.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, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
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 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.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.