Smit Barmase
aa1cb9c1e1
We recently fixed the issue of `cx.notify` on every mouse move event https://github.com/zed-industries/zed/pull/32408. As this perf bug was there for a long time, we made some not-optimal choices for checking things like if the mouse is hovering over an element in the prepaint phase rather than the `mouse_move` listener. After the mentioned fix, it regressed these code paths as prepaint is not being called for every other frame, and hence the mouse hovering logic never triggers. This bug is directly noticeable when the "cursor_blink" setting is turned off, which notifies the editor on every second. This PR fixes that for git inline blame popover by moving logic to show/hide in `mouse_move` instead of prepaint phase. `cx.notify` is only get called only when popover is shown or hidden. Release Notes: - Fixed git inline blame not correctly showing in Editor on hover when `cursor_blink` is `false`.
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.