Andrew Lygin
1aa9c868d4
How it looks: https://github.com/zed-industries/zed/assets/2101250/f564111c-1019-4442-b8a6-de338e12b12e This PR adds cursor markers to the scrollbar. They work similar to VSCode: 1. A cursor marker takes the whole scrollbar width. 2. It's always 2px high. 3. It uses the player's `cursor` color, so it may be helpful in the collaboration mode. There's a setting to switch cursor markers on/off: ```json { "scrollbar": { "cursors": true } } ``` Implementation details: - Unlike other markers, cursor markers are displayed synchronously. Otherwise they don't feel smooth and sometimes freez on prolonged up/down navigation. - Cursor markers are automatically switched off when it's more than 100 of them. - The minimum (non-cursor) marker height is now 5px. It allows the user to see other markers under the cursor marker. - The way the minimum height is imposed on markers has changed a bit to keep consistency between markers of different types. - Selected symbol markers use less vibrant color (`info` faded out a little). Release Notes: - Added displaying of cursor markers in the scrollbar. They can be switched on/off by the `scrollbar.cursors` setting.
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew tap homebrew/cask-versions
brew install zed-preview
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.