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

Support for terminal graphics protocols #31

Open
dhruvkb opened this issue Sep 12, 2024 · 0 comments
Open

Support for terminal graphics protocols #31

dhruvkb opened this issue Sep 12, 2024 · 0 comments

Comments

@dhruvkb
Copy link

dhruvkb commented Sep 12, 2024

Problem

A few popular terminals like kitty and WezTerm support Kitty's terminal graphics protocol for rendering images in the terminal. Support for the protocol is coming to other terminals like Warp.

Images rendered via the Kitty protocol are effectively rendered as blank spaces in to-html.

Solution

It would be great if this could be captured in to-html. I think the Kitty transmission medium where data is sent directly (t=d) as base-64 encoded RGB/RGBA (f=24/f=32) would be easiest to add support for.

Alternatives

iTerm2 has its own image protocol. There is also Sixel. These are more convoluted, less powerful and less widely supported (compared to Kitty's protocol) so this issue is not requesting those to be supported.

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

1 participant