I use chafa extensively, and it really is the best tool for terminal graphics in my opinion.

I use it as a fallback option for terminals without proper terminal graphics support in my TUI Jupyter client, euporie.

wonger_ a day ago | parent | next [-]

And I'm half-working on Rust bindings...

	▲	hectorm a day ago \| parent [-]
		Author of the JS bindings here. I also have a browser demo: https://ansi-o-matic.molinero.dev

Abishek_Muthian a day ago | parent | prev | next [-]

Have you tried Charmbracelet's bubble tea - https://github.com/charmbracelet/bubbletea

	▲	nairadithya a day ago \| parent [-]
		BubbleTea is great, but it doesn't have support for Kitty Graphics. https://github.com/charmbracelet/bubbletea/issues/163

tasuki a day ago | parent | prev | next [-]

> and it really is the best tool for terminal graphics in my opinion

Not sixel or kitty graphics?

	▲	mmulet a day ago \| parent \| next [-]
		One of the really cool things about chafa is that it has both sixel and kitty graphic renderers! (and iterm2 images as well) So you can output kitty if the terminal supports it, but fall back to ascii if it doesn’t.
	▲	hecanjog a day ago \| parent \| prev \| next [-]
		What interests me about it is the unicode mosaic output format that looks higher quality than the usual upper half block or braille character approaches without needing to support a special protocol.
	▲	robot-wrangler a day ago \| parent \| prev [-]
		Setting aside the usual compatibility issues with those things.. neither are available from your buildbot. Also while Jupyter does supports images other notebooking ecosystems may not, and anyway you need a file whereas chafa can work with streams.

lawlessone a day ago | parent | prev [-]

i'm curious do you work entirely with a terminal and no desktop?

Chafa looks cool, i'd feel cool using it when i use a terminal but if really wanted to see an image id just open it in a image viewer.