Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[FEAT] Configurable or environment-based logos

未关闭
#2,194 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
c, shell

调研方向

首先阅读 issue 中提到的 logo 自动检测入口点和 command module 配置,然后将它们与现有的 custom module 配置进行比较。定义基于环境或命令的 override 应如何回退到正常检测,并将 MSYS2 和 FreeBSD 的示例作为验收用例。

由索引模型根据 Issue 内容生成。

描述

enhancement
Description

It would be nice to be able to be able to alter the logo based on certain environment factors. For example, I share most of my configs across Windows, MSYS2, FreeBSD, and a couple Linux boxes. For most of them (and every individual unique OS) this works and prints the OS logo. However commit 23bccc4 added an MSYS2 logo to the set, but this can only be printed by manually specifying it. Similarly, FreeBSD has a Linux emulation layer to help make some less portable software work.
For both of those cases, it would be nice if something made it possible to override the logo based on e.g. an environment variable check, or some other probing mechanism, or perhaps even just as a check that can be specified in the configuration, similar to how custom modules work.

For the configuration option, it could look something like:

"logo": {
  // Run the specified command and use its output,
  // fall back to normal auto detect behavior is output is empty
  "detect": "if [ \"$MSYSTEM\" -ne \"\" ]; then echo Msys2 ; fi"
}
Motivation

The command module does not allow overriding the logo

Additional context

No response

主要语言
C
星标
24.7k
派生
895
平均合并
22 小时 43 分钟
30 天内合并 PR
20

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fastfetch-cli/fastfetch 的其他 Issue

查看 fastfetch-cli/fastfetch 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。