44d91c1709d0acc70e69dc0978333e69d28cb17c
## Summary Adds explanations for what each type of scrollbar indicator visually represents in the editor. ## Description This PR addresses the issue where users didn't understand what the colored marks on the scrollbar mean. The existing documentation explained how to toggle each type of mark on/off, but didn't explain what they actually represent. This adds a brief, clear explanation after each scrollbar indicator setting describing what that indicator shows (e.g., "Git diff indicators appear as colored marks showing lines that have been added, modified, or deleted compared to the git HEAD"). ## Fixes Closes #31794 ## Test Plan - Documentation follows the existing style and format of `docs/src/configuring-zed.md` - Each explanation is concise and immediately follows the setting description - Language is clear and user-friendly 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, Linux, and Windows you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- 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.
Description
GPUI – Community Edition maintained by Oak Team
https://gpui-ce.github.io/
257 MiB
Languages
Rust
95.5%
WGSL
1.2%
Metal
1.1%
HLSL
1.1%
Python
0.7%
Other
0.3%