080ef043c3
Closes #30091 Follow-up to #29958 This PR fixes the profile menu flickering due to the documentation aside after updating the agent dock position over the settings file. The problem arose because the `documentation_side` could get out of sync with the actual agent panel dock position. The `documentation_side` was only updated whenever the user changed the agent panel position using the UI, but not when updating the position in the settings file. You can reproduce this easily by changing the `agent.dock` position to the opposite site in your settings, which will make the profile menu flicker again in some scenarios due to the de-sync. This PR fixes this behavior by computing the position during render, thus the actual set panel position and the documentation position can never get out of sync Release Notes: - Fixed the agent profile menu flickering after updating the assistant panel dock position in the settings.
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.