can not preview image by wezterm imgcat

[nothyh]

background

problem

i can view image by wezterm imgcat in command line, but can not preview in lf

in command line

in lf

the previewer

in lf

and if i press any key the bottom of lf will change i can preview image by chafa in lf, but it is not clear, so i am trying to find another method to preview. i ask ai, he tell me because the communication between lf and wezterm has broken, but i do not know how to solve it

[nothyh]

more info

i use wezterm + tmux + lf

[CatsDeservePets]

Wezterm uses the iTerm protocol, which causes lots of problems, as seen in #2040.

[nothyh]

Wezterm uses the iTerm protocol, which causes lots of problems, as seen in #2040.

then if i want to use wezterm + lf, any tool to preview image clear, previewing by chafa is not clear

[veltza]

i can preview image by chafa in lf, but it is not clear,

What do you mean by Chafa is not clear? What version are you using?

[joelim-work]

The way previewer scripts work for different types of output is as follows:

• ueberzug draws the image on a separate window which is overlaid on top of the terminal. Because it does not affect the terminal at all, there is no need to output anything.
• For kitty, images are drawn independently from text (CMIIW), and since there are separate commands for drawing and clearing an image (sent directly to /dev/tty), this is handled by the previewer and cleaner scripts, which also do not output anything.
• sixel is different in the respect that text and images draw over each other. This means that clearing (writing spaces all over the preview window) cannot be done in the cleaner script as it runs asynchronously, as it might clear a text-based preview (e.g. if the user switches from an image to a text file). Hence, the actual drawing of sixel images is done by lf itself, to ensure that they are cleared properly. In this case, the sixel image itself is the output of the previewer script, and lf distinguishes this from text data by scanning for the ESC+P terminal sequence.

iTerm2 protocol would work similarly to sixel, except that it is not supported by lf because it does not detect the ESC]1337 terminal sequence. Maybe it would be possible to add built-in support for this, but then I'm not sure if it is worth it since the iTerm2 terminal can support sixel anyway.