[FEAT] Allow specification of fall-back logo
维护者通常 1 天内回复
还没有人认领这个 Issue。
- #2723 来自 @Remirdy —— 已关闭,未合并
评估
调研方向
Start by reading the logo configuration and rendering entry points to see how the configured logo type is selected and how unsupported terminal protocols are handled; the issue does not name specific files or tests. Done means a config can specify a primary Kitty logo and a fallback file logo, with the fallback displayed when Kitty graphics are unavailable.
由索引模型根据 Issue 内容生成。
描述
Description
Would it be possible to add an additional option to the logo handling to allow us to specify a fallback logo?
Motivation
I'm using Ghostty (latest 1.4.0 just released with full kitty support) and previously Kitty.
When SSH'ing into my servers (or indeed locally on my macbook), fastfetch will happily use the kitty option and display a PNG (and now an animated GIF). It looks great.
Occasionally, I may connect to my servers from another machine (e.g. a Windows host with Terminal) that does not support the Kitty graphics protocols. In this case, fastfetch cannot display the PNG/GIF and appears to fall-back to the default detected OS logo.
I have worked around this by keeping 2 fastfetch configs per machine; one with a kitty logo and another with a custom ASCII logo. Then bashrc uses a brief conditional to check the terminal and then run fastfetch pointing at the appropriate config.
It would be great to not have to do this with a script, and instead have the ability to specify the fall-back image natively in the fastfetch config.
In my case, primary logo would be the kitty logo (with the kitty type, file location, sizing etc), and then a fallback block with the file type, file location etc.
Obviously I don't know how feasible this is, but this would mean I could maintain a single fastfetch config for my servers.
Additional context
No response
- 主要语言
- C
- 星标
- 25.4k
- 派生
- 947
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 21
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
fastfetch-cli/fastfetch 的其他 Issue
-
[LOGO] VentoOS未关闭logo request
难度 1/5 1 小时以内 新手友好度 80/100
fastfetch-cli/fastfetch#2742 ·
维护者通常 1 天内回复
-
[LOGO] MacroMag OS可能已有人在做 @maldyrek 于 1 天前认领。 未关闭logo request
难度 2/5 1-3 小时 新手友好度 76/100
fastfetch-cli/fastfetch#2740 ·
维护者通常 1 天内回复
-
logo request
难度 2/5 1-3 小时 新手友好度 67/100
fastfetch-cli/fastfetch#2713 · 1 条评论 ·
维护者通常 1 天内回复
-
[LOGO] Visnux Linux可能已有人在做 @rafaelsoje 于 19 天前认领。 未关闭logo request
难度 2/5 1-3 小时 新手友好度 74/100
fastfetch-cli/fastfetch#2700 ·
维护者通常 1 天内回复
-
[LOGO] ZelixOS可能已有人在做 @Hwi0228 于 24 天前认领。 未关闭logo request
难度 2/5 1-3 小时 新手友好度 72/100
fastfetch-cli/fastfetch#2685 · 1 条评论 ·
维护者通常 1 天内回复
查看 fastfetch-cli/fastfetch 的全部 Issue
相似的 Issue
-
bug sev-3
难度 2/5 1-3 小时 新手友好度 62/100
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
SanderMertens/flecs#2444 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100