-
-
Notifications
You must be signed in to change notification settings - Fork 681
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
[Feature Request] - Implement kittys terminal graphics protocol #2814
Comments
FIY: On the yazi wiki, there's a fix to use it with tmux: https://github.com/sxyazi/yazi/wiki/Image-preview-within-tmux |
Is there a sense of the work required to implement this? |
Yes, but it's extremely slow on tmux for some reason. |
There's a plethora of users that want to enjoy images in their terminal and some terminal tools implement image support (image.nvim plugin for neovim, neorg plugin for neovim, a lot of file browsers, etc.). I almost never leave terminal and currently use tmux, image implementation in zellij would be a dealbreaker for me. |
I really want to see Zellij support kitty graphics protocol, which is currently the most complete and advanced. It supports Unicode placeholders, I think this could solve the stuttering issue in Zellij's Sixel implementation. Kitty protocol simply prints some escape sequence to the screen, and terminals that support that protocol display it as an image and accurately render the image position when scrolling. This process is transparent to Zellij, and it doesn't need to parse and understand the meaning of the protocol itself, making it efficient. I've just implemented Unicode placeholders for Yazi and tested it in kitty+tmux, it works well: kitty+tmux.mp4 |
@sxyazi I've also tested it under tmux and it kinda works, but everything is really buggy (overlapping images, preview not updating, etc.) for some reason. |
Yes, Zellij does not support it; this requires Zellij to provide support.
What are your Yazi version and tmux version? What terminal are you using? Please also do an |
Just came across this and thought I should chime in. I believe what's required on zellij's end is a Passthrough sequence (I don't know if such exists yet but I suspect not) i.e some something like this. No special handling of graphics control sequences should be required. This should be all that's required to get Kitty's virtual placements working, assuming Zellij already supports indexed- (and optionally, direct-) -color SGR sequences and passes them through as recieved. It'll also allow the use of other image/graphics protocols to a certain extent, particularly in full-screen (non-scrolling) applications. For full/proper support, specialized implementations/handling will be required but personally, I'd discourage that for a terminal multiplexer. |
This is also how this issue was solved with junegunn/fzf junegunn/fzf kitty image protocol passthrough fix He uses a regex to detect the terminal sequence for images then assigns a no-op function for the preview that allows the un-altered terminal sequence to passthrough to the terminal so that the image is rendered like normal. You can test this with: fd . ~/Pictures -e png | fzf --preview='kitty icat --clear --transfer-mode=memory --stdin=no --place=${FZF_PREVIEW_COLUMNS}x${FZF_PREVIEW_LINES}@0x0 {}' |
is this still being worked on? |
I don’t think anyone has started to implement this. Just been talking about ways in which it could be achieved |
I've been digging into this a bit more since I would like to see it implemented. It seems that zellij uses alacritty's vte parser to interpret ANSI/VT codes in |
Fwiw I've tried the following:
❯ neofetch
██████████████████ ████████ jimc@kapua
██████████████████ ████████ ----------
██████████████████ ████████ OS: Manjaro Linux x86_64
██████████████████ ████████ Host: NH5x_NH7xHP
████████ ████████ Kernel: 6.1.99-1-MANJARO
████████ ████████ ████████ Uptime: 10 days, 15 hours, 22 mins
████████ ████████ ████████ Packages: 3373 (pacman), 75 (nix-user), 48 (nix-default)
████████ ████████ ████████ Shell: zsh 5.9
████████ ████████ ████████ Resolution: 1920x1080
████████ ████████ ████████ DE: GNOME 46.3.1
████████ ████████ ████████ WM: Mutter
████████ ████████ ████████ WM Theme: Custom-Accent-Colors
████████ ████████ ████████ Theme: Adw-dark [GTK2/3]
████████ ████████ ████████ Icons: Papirus-Dark-Maia [GTK2/3]
Terminal: kitty
CPU: 11th Gen Intel i7-11800H (16) @ 4.600GHz
GPU: Intel TigerLake-H GT1 [UHD Graphics]
GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q
Memory: 41611MiB / 64087MiB |
@quadespresso That's great news, I didn't know it worked in Wezterm. Thank you for looking into this 👍 I've been using Alacritty for years and really missed the support for displaying images in the terminal and also ligatures. A few weeks ago decided to switch to Kitty and was somewhat surprised that images were not rendered in Zellij. After reading your comment I switched to Wezterm and everything works perfectly. 🥰 A funny thing was that when I, in Wezterm, attached to a running session started with Kitty, the images were not displayed. I had to close the session and restart it.
|
@merikan interesting test scenario. Based on that, I tried the opposite: I ran wezterm -> zellij -> yazi then navigated to an image to view. Then I detached from the zellij session, reconnecting from a kitty terminal. It was a bit of a mess, an entire screenful of characters. Nothing vaguely resembling yazi was to be seen. |
@quadespresso I couldn't resist, but also had Alacritty connected to the same session and there everything looked ok, except that the image is not displayed as we already know. Kind of fun to look at multiple clients connected to the same session when jumping around in Yazi 😁 |
@merikan it's always interesting to cross-check with alternatives. I ended up trying the same combo with Alacritty and saw the same, ie, yazi doesn't display the image, but is otherwise intact. Had a quick go with a few other terminal emulators (Terminator, Terminology, GNOME Terminal, Tilix), but only got as far as doing a quick check with yazi (minus zellij) to verify it couldn't display images before proceeding beyond that. I couldn't recall whether any of those supported inline images, and figured this would be quicker than pulling up docs for each. |
@quadespresso Which version of "Wezterm + Zellij + yazi" that can display image?
|
None. Zellij would have to implement some form of a passthrough ansi sequence that wraps image protocol sequences that indicate that the sequence should be let through the multiplexer. tmux/wiki/FAQ#what-is-the-passthrough-escape-sequence-and-how-do-i-use-it Im pretty sure zellij just strips the escape code which leaves a mess of base64 image data currently |
@hongquan here we go:
What's odd is that as I tested this today, I got nothing when I navigated yazi to the image. Blank in the area where I expected to see the image, I then quit yazi, quit zellij, started yazi, verified that I could see the image, quit yazi, started zellij and then yazi, and then I could see the image without issue. |
@quadespresso
|
I found this in the Zellij Discord server might be helpful (Quote from @imsnif in https://discord.com/channels/771367133715628073/771367133715628076/1272810902458204191):
|
A side effect of this is nushell is unusable in zellij when its |
AFAIK the kitty graphics and keyboard protocol are separate and don't require each other, are you sure your comment is on the right issue? |
Is this an issue of either move to WezTerm or change to Tmux? |
I can confirm that images does not display when using Ghostty Terminal. Ghostty does support the Kitty graphics protocol and images are displayed in Yazi when not in Zellij.
|
Ghostty+yazi works, Ghostty+zellij+yazi doesn't work. Ghostty 1.0.1-arch |
It would be neat if zellij could use kitty terminal graphics to display images or other files. Tmux had a similar issue closed, it seems like they will not be implementing it. Zellij does provide support for sixels but this is a very old protocol with not much support from other applications.
The text was updated successfully, but these errors were encountered: