o2sh/onefetch

Config file for theming/customization💄

Open

#745 创建于 2022年8月20日

在 GitHub 查看
 (20 评论) (4 反应) (0 负责人)Rust (5,179 star) (188 fork)batch import
discussionenhancementgood first issuehelp wanted

描述

Summary 💡

What about having a configuration file in which you could customize visual aspects of onefetch? for example:

General options:

  • The glyph to use for the separator (use "->" instead of ":")
  • The padding between the output and its surroundings
  • The spacing between the separator and the info
  • The text colors (would be equivalent to --text-colors)
  • Whether to hide the ASCII logo
  • image path to display by default instead of the ASCII logo
  • ...

Palette:

  • Which glyph to use for the palette (use "●" instead of " ")
  • Whether to hide the palette.
  • ...

Info lines:

  • Define the text to display as a title for each info lines (use "🖴" instead of "Size")
  • ...

The configuration file could be placed in ${HOME}/.config/onefetch/config.conf (which format? YAML? TOML?)

As suggested by @spenserblack

  • Add CLI flag to provide a different path to the config file

Motivation 🔦

Allow users to customize the look and feel of onefetch by creating themes and config files that can be shared and enjoyed by others.

For reference --> https://github.com/Chick2D/neofetch-themes and https://github.com/spenserblack/repofetch (for an example of implementation)

贡献者指南

技术栈
rust
领域
cli
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
RustCLI toolsconfig file parsingonefetch codebase
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Review the issue comments for design discussions, particularly around config file format (TOML vs YAML) and path location (e.g., ~/.config/onefetch/config.conf). Examine the existing CLI argument parsing in the repository (likely in src/cli.rs or similar) to understand how to integrate override logic. Check if there are any related PRs or branches. The maintainer may have provided guidance on the expected structure; look for comments from @o2sh or @spenserblack.