Dmitry NefedovandOleksiy Syvokon
38f4e21fe8
This PR makes zed terminal gruvbox theme consistent with other terminals themes. Current ansi colors is broken, by not only not using colors from original palette, but also by inverting of bright/normal colors... Currently I took colors from Ghostty (Iterm2 themes), making sure that they are consistent with palette. For dim colors I darken them by decreasing "Value" from HSV representation of colors by 30%. I am open to discussion and willing to implement those changes for light theme after receiving feedback. Examples below: | Before | After | | - | - | | <img width="489" height="472" alt="image" src="https://github.com/user-attachments/assets/599dd162-6666-4705-adb7-1b62a7800f70" /> | <img width="490" height="470" alt="image" src="https://github.com/user-attachments/assets/fee02cc5-6ca8-4daa-88f1-7f37f27f2ce4" /> | Script to reproduce: ```bash #!/bin/bash echo "Normal ANSI Colors:" for i in {30..37}; do printf "\e[${i}m Text \e[0m" done echo "" echo "Bright ANSI Colors (Foreground):" for i in {90..97}; do printf "\e[${i}m Text \e[0m" done echo "" echo "Bright ANSI Colors (Background):" for i in {100..107}; do printf "\e[${i}m Text \e[0m" done echo "" echo "Foreground and Background Combinations:" for fg in {30..37}; do for bg in {40..47}; do printf "\e[${fg};${bg}m FB \e[0m" done echo "" done echo "Bright Foreground and Background Combinations:" for fg in {90..97}; do for bg in {100..107}; do printf "\e[${fg};${bg}m FB \e[0m" done echo "" done ``` Release Notes: - Fixed ANSI colors definitions in the Gruvbox theme (thanks @dangooddd) --------- Co-authored-by: Oleksiy Syvokon <oleksiy@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.
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.