Xin Zhao
e1f73a61fe
Although `poetry` may store virtual environments in a global cache directory (unlike the standard project-local `.venv`), the internal directory structure of these environments remains consistent with standard `venv` or `uv` environments. Since our existing activation logic for `venv` environments relies on relative paths within the environment root, it is naturally compatible with `poetry` environments. Once the toolchain locates the environment's root directory, the activation scripts can be applied without further modification. Testing: - Verified on Windows: Confirmed working across `PowerShell`, `Pwsh`, and `Cmd` for global poetry environments. - Observation: When using an in-project `.venv` directory, the toolchain may categorize the environment as `venv`-managed instead of `poetry`-managed. While this behavior relates to the toolchain's discovery logic, the activation itself remains fully functional as the underlying structure is compatible. Release Notes: - N/A *or* Added/Fixed/Improved ...
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.