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

iTerm2 image protocol support broken in v0.2.8 #999

Open
imgurbot12 opened this issue Mar 3, 2025 · 3 comments
Open

iTerm2 image protocol support broken in v0.2.8 #999

imgurbot12 opened this issue Mar 3, 2025 · 3 comments

Comments

@imgurbot12
Copy link

imgurbot12 commented Mar 3, 2025

Hello, this is my first time using rio but I've run into an issue whilst using yazi to view images in the termal.

iTerm2 image protocol support seems to be broken in v0.2.8 as far as I can tell even on the latest rio-git version.

Rio version: v0.2.8
installation method: arch repostitory rio package and AUR rio-git (tested using both)
OS: EndeavourOS
DE: Hyprland 0.47.1
imgcat: PyPI

Image

@imgurbot12 imgurbot12 changed the title iTerm2 imgcat support broken in v0.2.8 iTerm2 image protocol support broken in v0.2.8 Mar 3, 2025
@raphamorim
Copy link
Owner

Hey @imgurbot12 thanks for the issue,

I tried to reproduce locally without success

Image

@raphamorim
Copy link
Owner

Using chafa Image

@imgurbot12
Copy link
Author

imgurbot12 commented Mar 3, 2025

Hey @raphamorim, thanks for the response.

I tried using chafa and ran into the same issue of an empty response with no rendered image. I notice in your screenshot you're using MacOS. I think this might be a Linux & Wayland specific issue. I tried using both Hyprland and Sway and it failed. I installed the x11 deb version within an Ubuntu VM and that worked whilst the wayland version did not.

I also tried changing the renderer in Hyprland from automatic to gl and vulkan with no success.

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

2 participants