Display / type buffer corruption

This happened to me upgrading to the next version after 2.0.3 (2.10?) The behavior was so disastrous for me that I have downgraded to 2.0.3.

To reproduce: paste a command line that is very long, ideally that wraps more than two, perhaps three, lines. Effect:
the right half of the display is totally wiped about from the middle down. The command (it needs to be one that normally works) produces weird errors (such as: python3 - command not found). That weird-format command is maintained in the history.

As a user, it is hard for me to tell if the corruption happens to the display buffer, the commandline buffer, or both. It definitely happens to the commandline buffer, because the command is retained weird in the cl history and, when run from the history, reproduces the same error.

It is not clear to me from the version history if it has been fixed in the latest version on the app store, so i am staying with 2.0.3 for now.

Like I say, if your workflow includes repeatedly pasting long command lines, this corruption is devastating. There is no way that I know to clear it.

Thank you A LOT for a-shell and for addressing this issue.

No source file, test, or entry point is named. Reproduce on iOS by pasting a working command long enough to wrap across several lines, compare the display and stored history with version 2.0.3, and consider the issue done when the command and terminal display remain intact and the command runs correctly from history.

Written by the indexing model from the issue text.