[FEAT] Allow specification of fall-back logo

Ouverte
#2,691 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

  • #2723 par @Remirdy — fermée sans fusion

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
c
Domaine
cli

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
C
Étoiles
25.4k
Forks
947
Merge moyen
1 j 8 h
PR mergées (30 j)
21

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fastfetch-cli/fastfetch

Toutes les issues de fastfetch-cli/fastfetch

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.