[FEAT] Allow specification of fall-back logo

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #2723 来自 @Remirdy —— 已关闭,未合并

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
cli

调研方向

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 内容生成。

描述

enhancement
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

环境准备

从这里开始

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

fastfetch-cli/fastfetch 的其他 Issue

查看 fastfetch-cli/fastfetch 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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