-
-
Notifications
You must be signed in to change notification settings - Fork 274
Added four new themes to the themes directory #1571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@neiljp |
Differences in Gruvbox Variants:
|
This table highlights the differences in foreground and background colors for each style between the two themes. The high-contrast theme uses bolder and more vibrant colors, while the original Gruvbox Dark theme uses more subdued tones. |
@Gopinath-Mahendiran I've not looked through every change, since your commits aren't tidied as per the main Zulip commit guidelines, and they're not passing tests - which may be related. Otherwise, the first thing that looks concerning after manual testing is that background color(s) don't match what I believe are those for any of the hard/medium/soft variants of either gruvbox theme, which I understand to be the Looking at the changes over all your commits, the other confusing large-scale changes are:
The source for the color scheme in vim, linked from the color scheme source, may well be useful to understand when certain colors are used, since it doesn't just show the colors and names, but also how they vary with these 'variants'. As I said, I've not studied the gruvbox themes except as per the background color. Right now your stated changes are expressed in the PR, but are difficult to translate. With a dynamic approach, with the theme behaving like a template, these variations would be explicit. We could start with the background color variation between variants, since that's extracted already, and then move from there. The Zulip guide has a lot more information, but to give you an idea of how you might structure your commits, I would suggest commits with minimal changes to individual files for the simplest change you can make to achieve the smallest next step. If they are independent they can be reordered later, and/or combined using an interactive rebase. For example, you might add some 'colors' first, but that could be split up into commits for only-dark, only-light, and maybe multiple for different color additions; later they might all be combined into a commit that relates to just all new colors, or one with the dark changes combined with code that uses those new dark changes for a background, for example. |
What does this PR do, and why?
This PR adds four new themes to Zulip Terminal, enhancing user customization options and improving the overall visual experience. The newly introduced themes offer greater flexibility for different user preferences.
Added new theme are
->gruvbox_dark_high_contrast
->gruvbox_dark_low_contrast
-> gruvbox_light_high_contrast
-> gruvbox_light_low_contrast
Outstanding aspect(s)
External discussion & connections
topic
How did you test this?
Self-review checklist for each commit
Visual changes
gruvbox_dark_low_contrast

gruvbox_dark_high_contrast

gruvbox_light_high_contrast

gruvbox_light_low_contrast
