Skip to content

Conversation

@Frost-Phoenix
Copy link
Contributor

@Frost-Phoenix Frost-Phoenix commented May 20, 2025

Hello, I made a dark-hard version of the existing gruvbox theme.
This is not a completely new theme, but I think it is different enough from the existing gruvbox theme to be relevant.

I really would like to get your opinion on this and on the theme itself.

image

Summary by CodeRabbit

  • New Features
    • Introduced a new Gruvbox Dark Hard theme option, offering updated color schemes for UI elements and code syntax highlighting.
    • Added documentation entry showcasing the Gruvbox Dark Hard theme with author credits and visual preview.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 20, 2025

Walkthrough

A new theme configuration file, gruvbox-dark-hard.toml, has been introduced in the theme directory. This file provides static color definitions and UI styling based on the Gruvbox Dark Hard palette, specifying colors for various interface elements and code syntax highlighting. Additionally, the theme list documentation was updated to include an entry for "Gruvbox Dark Hard" with author attribution and an illustrative image. No executable code or logic was added or modified.

Changes

File(s) Change Summary
src/superfile_config/theme/gruvbox-dark-hard.toml Added new TOML configuration file defining Gruvbox Dark Hard color scheme and UI element styles.
website/src/content/docs/list/theme-list.md Added "Gruvbox Dark Hard" theme entry with author info and illustrative image to theme list docs.

Poem

In the land of code where colors bloom,
A Gruvbox theme now lights the room.
Dark and hard, the palette glows,
With borders, hints, and modal shows.
Rabbits hop through hues so bold—
A cozy warren, warm and gold!
🐇🎨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
src/superfile_config/theme/gruvbox-dark-hard.toml (2)

1-6: Grammar and clarity in header comments
There are a few minor typos and consistency issues in the comment block:

  • Change “Theme create by:” to “Theme created by:”
  • Complete or remove the “Update by(sort by time):” line since it’s empty
  • Change “Thanks for all contributor!!” to “Thanks to all contributors!”

43-45: Improve gradient_color comment

  • Grammar: change “can only have two color!” to “can only have two colors.”
  • Consider aligning its header style (e.g., # ========= Gradient (two colors) =========) to match other sections.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 1a940d7 and 2b58989.

📒 Files selected for processing (1)
  • src/superfile_config/theme/gruvbox-dark-hard.toml (1 hunks)
🔇 Additional comments (9)
src/superfile_config/theme/gruvbox-dark-hard.toml (9)

10-10: Confirm code_syntax_highlight value
The style is set to "gruvbox". Please verify that this matches the intended Chroma style name (e.g. if you meant a distinct "gruvbox-dark-hard" style) or update as needed.


12-16: Border color definitions look consistent
The border colors follow the Gruvbox Dark Hard palette and adhere to the existing naming conventions. No issues found.


17-22: Active border colors are well-defined
Good contrast between inactive and active states; these values fit the “hard” variant.


23-29: Background colors are consistent
All background elements share the same base (#1D2021), which is typical for a cohesive dark theme.


30-36: Foreground (fg) settings look good
Using #FBF1C7 across all foreground elements ensures readability against the dark background.


49-51: Verify empty background values in File Panel
file_panel_item_selected_bg is set to an empty string. Confirm that the config loader treats this as “no background” rather than producing a parse error. If not, consider removing the key or providing a default.


53-56: Verify empty sidebar background value
Similarly, sidebar_item_selected_bg is empty. Ensure the parser handles empty strings gracefully or supply a fallback color if needed.


59-63: Verify empty modal background values
Both modal_cancel_bg and modal_confirm_bg are empty. Please check that empty strings are valid in your TOML loader; otherwise, remove these keys or add defaults.


66-68: Help Menu styling approved
The hotkey (#689D6A) and title (#B16286) colors fit well with the palette and maintain consistency.

@lazysegtree
Copy link
Collaborator

@Frost-Phoenix To prevent theme issues, we are adding these instruction for theme PRs.

Please add these screenshots in the PR, to make sure that the theme doesn't have any issues

  • Full view of superfile (Including sidebar, file previewer, process panel, metadata panel, and clipboard panel )
    • Make sure that file previewer is non empty, process panel has at least one process, and clipboard has at least one entry
  • Add a screenshot of these individual panel being focussed (To make sure border focus color is good)
    • Sidebar
    • Processbar
  • Add a screenshot of help menu (Press ?)
  • Add a screenshot of popup that opens when you create a new file (Ctrl+n)
  • Add a screenshot of image being preview using your theme.
  • Add a screenshot of successful and unsuccessful shell command.
Example

  • Full view of superfile (Including sidebar, file previewer, process panel, metadata panel, and clipboard panel )
    • Make sure that file previewer is non empty, process panel has at least one process, and clipboard has at least one entry
image
  • Add a screenshot of these individual panel being focussed (To make sure border focus color is good)
    • Sidebar
    • Processbar
image image
  • Add a screenshot of help menu (Press ?)
image
  • Add a screenshot of popup that opens when you create a new file (Ctrl+n)
image
  • Add a screenshot of image being preview using your theme.
image
  • Add a screenshot of successful and unsuccessful shell command.
image image

@lazysegtree
Copy link
Collaborator

@Frost-Phoenix What are the major points where it differs from gruvbox ?

@Frost-Phoenix
Copy link
Contributor Author

What are the major points where it differs from gruvbox ?

It is a variant of the same theme with a similar "atmosphere" but features different colors, mainly with higher contrast. This is comparable to the different Catppuccin variants (Mocha, Macchiato, Frappé, and Latte).

Here are both themes side by side:

Gruvbox Gruvbox Dark Hard
gruvbox gruvbox-dark-hard

I understand if you think it’s not different enough to be included in the theme list.

Screenshots

Full view of superfile

Sidebar panel

Processes panel

Help menu

New file popup

Image preview

About the shell commands, I dind't find how to open the dialog, what is the keybind to open it?

@lazysegtree
Copy link
Collaborator

@Frost-Phoenix Thanks. This looks different enough. Its has an "actual dark theme" vibe.

For shell panel you would build the branch from latest main.

@lazysegtree
Copy link
Collaborator

image image

Here - Screenshots for shell

@lazysegtree
Copy link
Collaborator

This looks good.

Please also add a file for this in
assets/

and update the list in

website/src/content/docs/list/theme-list.md

refer to this

https://github.com/yorukot/superfile/pull/673/files

@Frost-Phoenix
Copy link
Contributor Author

This looks good.

Please also add a file for this in assets/

and update the list in

website/src/content/docs/list/theme-list.md

refer to this

https://github.com/yorukot/superfile/pull/673/files

Done!

Thanks for your review.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
website/src/content/docs/list/theme-list.md (2)

85-87: Convert bare URLs to markdown links
To satisfy markdownlint’s MD034 rule and improve readability, wrap the GitHub URLs in link syntax. For example:

- - Ported by: https://github.com/frost-phoenix
+ - Ported by: [frost-phoenix](https://github.com/frost-phoenix)
- - Original Author: https://github.com/morhetz/
+ - Original Author: [morhetz](https://github.com/morhetz/)
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

86-86: Bare URL used
null

(MD034, no-bare-urls)


87-87: Bare URL used
null

(MD034, no-bare-urls)


89-89: Add descriptive alt text to the theme preview image
Markdownlint MD045 flags images without alt text. Including a short description improves accessibility:

- ![](https://github.com/yorukot/superfile/blob/main/asset/theme/gruvbox-dark-hard.png?raw=true)
+ ![Gruvbox Dark Hard theme preview](https://github.com/yorukot/superfile/blob/main/asset/theme/gruvbox-dark-hard.png?raw=true)
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

89-89: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 2b58989 and 10931e7.

⛔ Files ignored due to path filters (1)
  • asset/theme/gruvbox-dark-hard.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • website/src/content/docs/list/theme-list.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
website/src/content/docs/list/theme-list.md

86-86: Bare URL used
null

(MD034, no-bare-urls)


87-87: Bare URL used
null

(MD034, no-bare-urls)


89-89: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

🔇 Additional comments (1)
website/src/content/docs/list/theme-list.md (1)

83-90:

✅ Verification successful

Verify that the new theme asset and config file are present
Ensure the repository includes both the gruvbox-dark-hard.toml configuration and the corresponding screenshot under asset/theme/. You can run:


🏁 Script executed:

#!/bin/bash
# Verify theme config and preview image were added
fd --type f gruvbox-dark-hard.toml
fd --type f gruvbox-dark-hard.png

Length of output: 156


Verification Complete: Theme Assets Present
Both the configuration file and preview image for “gruvbox-dark-hard” have been added:

  • src/superfile_config/theme/gruvbox-dark-hard.toml
  • asset/theme/gruvbox-dark-hard.png

No further action required.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

86-86: Bare URL used
null

(MD034, no-bare-urls)


87-87: Bare URL used
null

(MD034, no-bare-urls)


89-89: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

@lazysegtree lazysegtree merged commit 49dd522 into yorukot:main May 22, 2025
3 checks passed
tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request May 23, 2025
This MR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [yorukot/superfile](https://github.com/yorukot/superfile) | minor | `v1.2.1` -> `v1.3.0` |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>yorukot/superfile (yorukot/superfile)</summary>

### [`v1.3.0`](https://github.com/yorukot/superfile/releases/tag/v1.3.0)

[Compare Source](yorukot/superfile@v1.2.1...v1.3.0)

We are excited to release v1.3.0 for superfile, with new features, key bug fixes, and lots of polish under the hood.

#### Install:

[**Click me to know how to install**](https://github.com/yorukot/superfile?tab=readme-ov-file#installation)

#### Highlights

-   We have revamped the command prompt and added built-in commands for SuperFile-specific actions. Check out yorukot/superfile#745

-   Multi-panel startup support. You can now open multiple panels right from startup, making your workflow even more efficient.

-   Added new configurations :  --chooser-file option, show_panel_footer_info config flag and many command prompt specific flags.

#### Improvements & Fixes

-   The sidebar code was refactored and separated for better maintainability and various linter fixes and CI/CD improvements were made to keep the codebase clean and robust.

-   A new Rendering package is implemented, centralising border, content, and section rendering logic into reusable renderer components, fixing many layout bugs.

-   Model behaviour, file operations and rendering-related unit tests were added to improve test coverage.

#### Detailed Change Summary

<details><summary>Details</summary>
<p>

#### New Features

-   Added a Command-Prompt for SuperFile specific actions [`#752`](yorukot/superfile#752) by [@&#8203;Rocco-Gossmann](https://github.com/Rocco-Gossmann), [@&#8203;yorukot](https://github.com/yorukot)  and [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Allow specifying multiple panels at startup [`#759`](yorukot/superfile#759) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Initial draft of rendering package [`#775`](yorukot/superfile#775) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Render unit tests for prompt model [`#809`](yorukot/superfile#809) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Chooser file option, --lastdir-file option, and improvements in quit, and bug fixes [`#812`](yorukot/superfile#812) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Prompt feature leftover items [`#804`](yorukot/superfile#804) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   SPF Prompt tutorial and fixes [`#814`](yorukot/superfile#814) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Write prompt tutorial, rename prompt mode to spf mode, add develop branch in GitHub workflow, show_panel_footer_info flag [`#815`](yorukot/superfile#815) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Theme: Add gruvbox-dark-hard [`#828`](yorukot/superfile#828) by [@&#8203;Frost-Phoenix](https://github.com/Frost-Phoenix)

#### Updates & Improvements

-   Sidebar separation [`#767`](yorukot/superfile#767) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Sidebar code separation [`#770`](yorukot/superfile#770) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Rendering package and rendering bug fixes [`#781`](yorukot/superfile#781) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Refactor CheckForUpdates [`#797`](yorukot/superfile#797) by [@&#8203;JassonCordones](https://github.com/JassonCordones)
-   Rename metadata strings [`#731`](yorukot/superfile#731) by [@&#8203;booth-w](https://github.com/booth-w)

#### Bug Fixes

-   Fix crash with opening file with editor on an empty panel [`#730`](yorukot/superfile#730) by [@&#8203;booth-w](https://github.com/booth-w)
-   Fix: Add some of the remaining linter and fix errors [`#756`](yorukot/superfile#756) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Golangci lint fixes [`#757`](yorukot/superfile#757) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Fix: Remove redundant function containsKey [`#765`](yorukot/superfile#765) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Fix: Correctly resolve path in open and cd prompt actions [`#802`](yorukot/superfile#802) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Prompt dynamic dimensions and unit tests fix [`#805`](yorukot/superfile#805) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Fix: Convert unicode space to normal space, use rendered in file preview to fix layout bugs, Release 1.3.0 [`#825`](yorukot/superfile#825) by [@&#8203;lazysegtree](https://github.com/lazysegtree)

#### Optimization & Code Quality

-   Adding linter to CI/CD and fix some lint issues [`#739`](yorukot/superfile#739) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Linter fixes, new feature of allowing multiple directories at startup, other code improvements [`#764`](yorukot/superfile#764) by [@&#8203;lazysegtree](https://github.com/lazysegtree)
-   Model unit tests [`#803`](yorukot/superfile#803) by [@&#8203;lazysegtree](https://github.com/lazysegtree)

#### Dependency Updates

-   fix(deps): update dependency astro to v5.7.7 [`#726`](yorukot/superfile#726) by [@&#8203;renovate](https://github.com/renovate)
-   fix(deps): update module github.com/shirou/gopsutil/v4 to v4.25.3 [`#749`](yorukot/superfile#749) by [@&#8203;renovate](https://github.com/renovate)
-   fix(deps): update module github.com/pelletier/go-toml/v2 to v2.2.4 [`#760`](yorukot/superfile#760) by [@&#8203;renovate](https://github.com/renovate)
-   fix(deps): update module github.com/alecthomas/chroma/v2 to v2.16.0 [`#751`](yorukot/superfile#751) by [@&#8203;renovate](https://github.com/renovate)
-   fix(deps): update dependency sharp to ^0.34.0 [`#755`](yorukot/superfile#755) by [@&#8203;renovate](https://github.com/renovate)
-   fix(deps): update dependency [@&#8203;astrojs/starlight](https://github.com/astrojs/starlight) to ^0.34.0 [`#761`](yorukot/superfile#761) by [@&#8203;renovate](https://github.com/renovate)

</p>
</details> 

#### New Contributors
* @&#8203;Rocco-Gossmann made their first contribution in yorukot/superfile#736
* @&#8203;Frost-Phoenix made their first contribution in yorukot/superfile#828

**Full Changelog**: yorukot/superfile@v1.2.1...v1.3.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC4yMi4wIiwidXBkYXRlZEluVmVyIjoiNDAuMjMuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90Il19-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants