Closes #55728 ## Summary The Windows installer writes the localized Windows 11 Explorer context menu title to `HKCU\Software\Classes\{RegValueName}ContextMenu`, where the release channels use `Zed`, `ZedPreview`, and `ZedNightly` as the registry value names. `explorer_command_injector.dll` was reading from `ZedEditor*ContextMenu` instead, so the registry lookup failed and Explorer always received the hardcoded `Open with Zed` fallback. This aligns the DLL registry paths with the installer-written keys for stable, preview, and nightly. ## Tests - `cargo check --package explorer_command_injector --no-default-features --features stable` - `cargo check --package explorer_command_injector --no-default-features --features preview` - `cargo check --package explorer_command_injector` - `cargo check --package explorer_command_injector --all-features` - `cargo fmt --check --package explorer_command_injector` - `git diff --check` Release Notes: - Fixed localized Windows Explorer context menu titles falling back to English. --------- Co-authored-by: MrSubidubi <finn@zed.dev>
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.