[FEAT] Allow specification of fall-back logo

Aberta
#2,691 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

  • #2723 de @Remirdy — fechado sem integrar

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
c
Domínio
cli

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
C
Estrelas
25.4k
Forks
947
Merge médio
1d 8h
PRs com merge (30d)
21

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de fastfetch-cli/fastfetch

Todas as issues de fastfetch-cli/fastfetch

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.