mirror of
https://github.com/zed-industries/zed.git
synced 2025-01-09 10:56:20 +00:00
Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
f1428fea4e
At the moment, the editor scrollbar is 12px wide. One pixel is allocated for the left border, so we have 11 pixels to display markers. It's not enough to make three even marker columns (git, highlights, diagnostics) that fully fill the scrollbar, so the current implementation allocates 3 pixels to each column. As the result, we have 2 spare pixels on the right (before #10080 they were occupied by the diagnostics column). Making the scrollbar just one pixel wider allows us to give one additional pixel to each marker column and make markers more pronounced ("as is" on the left, "to be" on the right): <img width="115" alt="zed-scrollbar-markers-1px" src="https://github.com/zed-industries/zed/assets/2101250/4bdf0107-c0f1-4c9c-9063-d2ff461e1c32"> Other options: - Remove scrollbar thumb border. That'll give us one missing pixel to make markers wide and even. I, personally, prefer this option, but themes now have `scrollbar.thumb.border` colors that differ from `scrollbar.thumb.background` for some reason. This theme setting becomes deprecated in this case. For the reference: VS Code doesn't have scrollbar slider borders, IntelliJ IDEA does have them. - Don't try to make markers evenly wide. For instance, IntelliJ uses very narrow git-diff markers that are separated from other markers. But it requires much wider scrollbar (it's 20px in IDEA). - Use the spare two pixels to make diagnostic markers wider (it's the pre #10080 approach), or split them between the highlight and diagnostic markers (have 3px+4px+4px marker columns). - Do nothing. It leaves us with two unused pixels :( Release Notes: - N/A Related Issues: - The previous discussion: https://github.com/zed-industries/zed/pull/9080#issuecomment-1997979968 |
||
---|---|---|
.cargo | ||
.config | ||
.github | ||
.zed | ||
assets | ||
crates | ||
docs | ||
extensions | ||
script | ||
tooling/xtask | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.mailmap | ||
Cargo.lock | ||
Cargo.toml | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
debug.plist | ||
docker-compose.sql | ||
docker-compose.yml | ||
Dockerfile | ||
LICENSE-AGPL | ||
LICENSE-APACHE | ||
LICENSE-GPL | ||
livekit.yaml | ||
Procfile | ||
README.md | ||
rust-toolchain.toml | ||
typos.toml |
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 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.
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 specified
error for a crate you've created? If so, addpublish = false
under[package]
in your crate's Cargo.toml. - Is the error
failed to satisfy license requirements
for 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 theaccepted
array inscript/licenses/zed-licenses.toml
. - Is
cargo-about
unable 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.