[FEAT] Allow specification of fall-back logo

Aperta
#2,691 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

  • #2723 di @Remirdy — chiusa senza merge

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
cli

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
C
Stelle
25.4k
Fork
947
Merge medio
1g 8h
PR unite (30g)
21

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fastfetch-cli/fastfetch

Tutte le issue di fastfetch-cli/fastfetch

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.