The other day I was testing the debugging feature and I noticed a **very** small visual bug. When you click on the breakpoint circle to set a breakpoint, the breakpoint color remains in the wrong state until the mouse moves. After debugging for a while, I noticed that the issue was that the PhantomVariableIndicator variable attribute `collides_with_existing_breakpoint` was not being updated until the mouse moved. With the following change, the attribute is updated when the user clicks the breakpoint, toggleling tha attribute. ### Prior behaviour: https://github.com/user-attachments/assets/3dfa8e25-e970-49a3-8e87-0ecadabb3a3c As you can see in the video, prior to this change, the breakpoint would only change to the correct color when the mouse moved. ### New behaviour https://github.com/user-attachments/assets/356e84dc-42e5-4440-afab-0fbc4b3a1f0a With this new change, the breakpoint updates right after the user clicks, no need to move the mouse. ### Disclaimers - I'm new to this codebase, so any feedback is extremely welcomed! If you know of a better place where this could be handled, let me know and I'll explore further. https://github.com/user-attachments/assets/12d4b9df-e5d7-4955-b58d-dd63563c5c1b Release Notes: - N/A --------- Co-authored-by: Anthony Eid <anthony@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 issue)
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
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.