Add an option to wait for key press after showing the image

[unxed]

...and delete it according to kitty protocol after any key is pressed

[hpjansson]

I'd rather not add this, since it's technically an interactive UI, and chafa is just a CLI tool that takes an input and spits out outputs. It's meant to be used with other shell utilities: you should be able to wait for input using read and remove images afterwards using clear.

In general, contemporary terminal graphics protocols have a lot of features that only make sense in interactive applications. I may write an interactive viewer at some point, but chafa as it currently stands isn't it.

There's a potential compromise solution here, though: We could print the IDs of the images we create to a stream (probably a file or FIFO, since stdout is for images and stderr is for errors). Then your script could read the IDs from the file and manipulate them itself.

[unxed]

There's a potential compromise solution here, though: We could print the IDs of the images we create to a stream (probably a file or FIFO, since stdout is for images and stderr is for errors). Then your script could read the IDs from the file and manipulate them itself.

It would be great, thanks! Also it would be great to insert image deletion into chafa itself, so that you could display an image, write the ID to a file, call read, and then execute chafa again with a some parameter that invokes image or images deletion by ID (or IDs) stored in the file.

At the same time, we in far2l team could replace the code that deletes all images after the command that created them completes with deleting the images before drawing panels on top of the terminal. This would essentially solve the problem; we'd just have to use a slightly longer one-liner instead of a single call to chafa.

UPD: The lead far2l developer solved the problem on our side by adding a wait for key to be pressed if the image displayed by the console program remained on the screen after program exiting.