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.
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.