Kyle Kelley
7cb01e42ef
Stops the `conda activate base` fallback in `PythonToolchainProvider::activation_script` for two cases: 1. A Conda toolchain whose `environment.name` is `None`. 2. A Conda toolchain whose name is `Some(...)` but `shell.try_quote` rejects it. Previously both cases pushed `conda activate base` into the activation script. With miniforge installed and no env explicitly selected, every terminal silently activated `(base)`. The user didn't pick `base`; injecting it is contamination. Both branches now log a warning and emit no activation line. Users who want `(base)` can select it as the toolchain explicitly. Two unit tests cover the new behavior: `test_conda_activation_skips_when_name_missing` (name=None) and `test_conda_activation_skips_unquotable_name` (name=Some but unquotable, exercised with an embedded NUL byte that `shlex::try_quote` rejects). The existing `test_conda_activation_script_injection` still verifies that quotable names get activated. Release Notes: - Fixed Zed silently injecting `conda activate base` into terminals when a Conda manager (miniforge/miniconda) was installed but no specific environment was selected.
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 discussion)
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
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
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.