Finn Evers
9693eab098
This PR resolves a small regression introduced by the debugger-introduction, which causes the active line number to no longer be highlighted in the gutter as long as it is not part of a selection. A user reported this issue [on Discord](https://discord.com/channels/869392257814519848/995403703894954060/1357153291913662567). Prior to the debugger-commit, an active line number was highlighted if it was part of the editor active line numbers: https://github.com/zed-industries/zed/blob/ed4e654fdf66fb886414198ac6db1a2f24d729a5/crates/editor/src/element.rs#L4295-L4303 With the debugger-introduction, the code was changed to only highlight lines which are part of a selection: https://github.com/zed-industries/zed/blob/e2aaf9b7046dd8d8430ff82554fe13d69431e443/crates/editor/src/element.rs#L2411-L2422 However, the check whether it is within a selection is not neccesary, as the line is an active line as long as it is within the map of active lines. This PR restores the previous behavior. | `main` | <img width="922" alt="main" src="https://github.com/user-attachments/assets/486a548d-fe09-450e-922e-1feb4366fb4f" /> | | --- | --- | | This PR | <img width="922" alt="PR" src="https://github.com/user-attachments/assets/80517880-14b5-4861-bf83-8364f7831c46" /> | Release Notes: - Fixed an issue where the active line number in the editor was not always highlighted.
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.