Marshall Bowers
a2424638f5
This PR improves the multibuffer hints added in #14668 to fix a few issues. The original implementation relied on bailing out early in `render` by returning an `Empty` element. However, this had the unintended side-effect that when initially opening a multibuffer (such as the project search) there would be additional whitespace increasing the height of the toolbar due to the empty element. The reason we were doing this in the first place was because the hints weren't updating when the item's breadcrumbs changed. We're able to address this properly by using a subscription to the item's events and recompute the visibility of the hint when the active item's breadcrumbs change. This also has the benefit of making the hints re-appear right away when running the `welcome: reset hints` command with a multibuffer open. Release Notes: - N/A
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.