-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
*WezTerm* supports the *Kitty* Image protocol now #473
Comments
Thanks. |
There's more to the problem than just detecting support. |
It kind of works but I wonder if wezterm supports completely the protocol. Resizing doesn't seem to work, for example. Kitty's spec specifies that "The image will be scaled (enlarged/shrunk) as needed to fit the specified area" and Wezterm doesn't seem to respect that. I've also another problem: the only way to correctly detect the support without having problems on some terminals seems to be to read an env var and there's no guarantee wezterm sets it in an adequate way. |
I made a comment over here: 0b15aed#r62986264 about detection
For the scaling issue, can you clarify for me what's happening? Are you using the https://github.com/Canop/broot/blob/master/src/kitty/image_renderer.rs#L192-L199 |
i can tell you that Notcurses is detecting it via terminal query |
https://github.com/dankamongmen/notcurses/blob/master/src/lib/in.c#L1243-L1250 |
This got lost along the way somewhere, but now it's back! refs: Canop/broot#473
I've fixed the scaling issue in wezterm! |
Not yet; they can use the nightly build for now |
What's the progress now? I found image rendering still not "full quality" on the nightly wezterm and the newest broot(on Windows). |
Per wez/wezterm#986, WezTerm now supports the Kitty image protocol.
The code at
broot/src/kitty/image_renderer.rs
Line 87 in 424023b
if term_name.contains("kitty")
. This can include WezTerm now too.The text was updated successfully, but these errors were encountered: