Force terminal features support from config

[salva-ferrer]

Disclaimer: I understand that what I am going to suggest may open a complex can of worms. I am able to fix it for my personal use, but maybe others find it useful.

My environment: I use Yazi as a daily fm, and also use alacritty for my terminal. I'm aware of alacritty's adamant position about sixel, and I have been using ayozec sixel patch for alacritty for some time now without any issue.

In previous versions of Yazi, the terminal capabilities were detected by yazi so I could use sixel images in my version of alacritty. That's what I remember.

In current versions of yazi, the terminal capabilities are hardcoded in the brand.rs file. So even if my terminal supports sixel, yazi will refuse to use sixel because the terminal identifies itself as alacritty.

My solution is to have a patch that redefines alacritty in brand.rs, apply it and recompile yazi as soon as I see an update breaks my previews.

My brainstorm is if you could allow to overwrite the default terminal support from the configuration file without causing too much mayhem in supporting potentially crazy configurations.

Another option that I can try on my end: what happens if my terminal identifies as something else, not in the list defined in brands.rs? would yazi probe the capabilities or default to caca or ueberzugg support?

Thanks in advance for reading!

[sxyazi]

Please try #2377

[salva-ferrer]

Indeed, cleaner solution than my suggetsions :).

Now yazi properly identifies sixel support in my patched alacrity. Thank you!!!