Entire screen flickers when rebasing a screen full of commits

[SuperSandro2000]

When I rebase ~50 commits the entire screen flickers every time I move the cursor.

[MitMaro]

Thanks for the report! What terminal and OS are you using?

[SuperSandro2000]

bash version 5.0.17(1)-release in tmux over ssh in a Windows Terminal Preview.

I suspect that it redraws the entire screen every time I move my cursor instead of only the relevant parts.

[MitMaro]

Thanks for the info. There isn't much that can be done here. Windows Terminal is fairly new and support for it is still not great. Hopefully, the team behind that project can improve the performance of the terminal.

I suspect that it redraws the entire screen every time I move my cursor instead of only the relevant parts.

This is tricky to do in a cross-platform way. Some terminals allow partial redraws, some do not. This may be something I decide to investigate and handle in the future.

I am also hoping that once crossterm-rs/crossterm#167 is addressed, I can do a proper double-buffer on render and the flicker should disappear.

[SuperSandro2000]

Windows Terminal is fairly new and support for it is still not great.

Not really. It supports almost everything a terminal should support. For example I can scroll all day in htop without anything flickering.

This is tricky to do in a cross-platform way. Some terminals allow partial redraws, some do not. This may be something I decide to investigate and handle in the future.

It should just work if you treat it like a normal Linux terminal. I am not using cmd I am using WSL in Windows Terminal which so far did support everything I threw it at like Konsole.

[nickolay]

I also see flickering in WezTerm on Windows 10. Per their advice I recorded the session and see that the "clear" command is flushed for some reason:

[44.986176,"o","\u001b[2J"]
[45.001392,"o","\u001b[4m\u001b[HGit Interactive Rebase Tool           

I'm not sure how to debug it, since the escape codes printed are very much different when running in VSCode's debugger.

Anyway there's a new feature in cross-term crossterm-rs/crossterm#756, which should help here.