Aaron Feickert
4ed3c133cf
A recent change in #22730 (to reduce workspace serialization) means that a dock "forgets" its active panel whenever it is closed. When opened again, the change in #22346 (which establishes a panel activation order) takes effect, always opening the highest-priority panel for that dock instead of the panel the user previously manually activated. The result is that if you have, say, the outline panel active on the right dock, and toggle the dock closed and then back open again, the assistant panel will always appear instead. This PR reverts part of the change in #22730 to ensure a dock remembers its active panel when it is closed. Closes #22923. Release Notes: - Fixed an issue where docks did not remember the active panel.
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.