Converting back to draft to avoid accidental merging, until the issues mentioned in #654 (comment) are resolved

@Porkepix could you try this PR again? I have reverted to a earlier viuer version for now, which still has icy_sixel support, but not the kitty issue. With this version i cannot reproduce the issue in wezterm.

@Porkepix could you try this PR again? I have reverted to a earlier viuer version for now, which still has icy_sixel support, but not the kitty issue. With this version i cannot reproduce the issue in wezterm.

I'd say it looks fine from little testing. I also saw you opened several issues upstream, maybe you should add it's clear regression between 0.10 and 0.11 then, running some bisect on it if you can build from local copy could help upstream.

Is viuer relying on the other create you opened an issue for this, or is it unrelated in the end?

maybe you should add it's clear regression between 0.10 and 0.11 then, running some bisect on it if you can build from local copy could help upstream.

I did mention in viuer that it is fine in 0.10.0, but broken in 0.11.0 and the PR that changed it and why practically everything is still affected, only that the PR made it more apparent.

EDIT: i re-read what i wrote in the viuer issue, i did not explicitly mention that 0.10.0 is fine, but even then, like i said 0.11.0 only made the issue more apparent.

Is viuer relying on the other create you opened an issue for this, or is it unrelated in the end?

It is related and unrelated.
The TL;DR is that both tui-realm (via crossterm) and viuer try to read the input (keys). Terminal responses to queries are simply also just "keys" and neither has proper stdin locking (not actually using std::io::StdIn for some reason), so it is a race condition to who gets it first (and viuer has a infinite loop to wait for the keys).

maybe you should add it's clear regression between 0.10 and 0.11 then, running some bisect on it if you can build from local copy could help upstream.

I did mention in viuer that it is fine in 0.10.0, but broken in 0.11.0 and the PR that changed it and why practically everything is still affected, only that the PR made it more apparent.

My bad, either I saw it before, or I just didn't read thoroughly enough then!