Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KDE Konsole supports images (chafa works) #128

Open
giorgiga opened this issue Oct 12, 2024 · 5 comments
Open

KDE Konsole supports images (chafa works) #128

giorgiga opened this issue Oct 12, 2024 · 5 comments

Comments

@giorgiga
Copy link

This is to let you know that KDE Konsole supports the terminal image protocol (in fact, it works with chafa). IDK since when.

@emk2203
Copy link

emk2203 commented Nov 16, 2024

KDE Konsole supports the kitty protocol as well. Unfortunately, without chafa, viu renders the unicode block in Konsole instead of the graphics.

@rhodes-b
Copy link

rhodes-b commented Jan 1, 2025

KDE Konsole supports the kitty protocol as well. Unfortunately, without chafa, viu renders the unicode block in Konsole instead of the graphics.

if you set TERM=xterm-kitty viu ...image it should work at least that does in ghostty, viu seems to do terminal name matching instead of querying for support as listed here, I also didnt see a way to pass it as a command line argument like fastfetch

not sure if a config file lets you do it properly I didnt wanna look into that

https://sw.kovidgoyal.net/kitty/graphics-protocol/#querying-support-and-available-transmission-mediums

image
image

@metal3d
Copy link

metal3d commented Jan 10, 2025

Actually, it works on many terminal emulators. Ghostty works perfectly too (without the need of chafa and without the need to change TERM env variable). Maybe the README should indicate it.

@rhodes-b
Copy link

rhodes-b commented Jan 10, 2025

Actually, it works on many terminal emulators. Ghostty works perfectly too (without the need of chafa and without the need to change TERM env variable). Maybe the README should indicate it.

care to explain further? without a config it does not display images using kitty image format for viu 1.5.0 just like how my post describes. My image shows a very clear example how it just works using kitty image protocol when you set term to xterm-kitty

I dont see anywhere in viu --help where I can set the output type either

@rhodes-b
Copy link

looking at the source of the library, it does term name matching so it will work in ghostty if your version is new enough. Again like I stated above its built into the kitty image protocol to query for image support instead of name matching terminals
https://github.com/atanunq/viuer/blob/f66fa7710ee82a2bfc03e259889445b797ac5709/src/printer/kitty.rs#L62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants