Editing command line can hang shell

[treyharris]

Just two keystrokes can cause the shell to become unusable.

Steps to reproduce

1. Open a LibTerm shell.
2. Type ls or another command, but do not execute it.
3. Press ⌃a to jump to the beginning of the line.
4. Press ⌃k to kill the remaining text on the line.

Expected result

The cursor moving to the l in ls and then ls deleted, allowing a new command to be typed.

Actual result

The cursor jumps to column 0 (at the beginning of the shell prompt) after ⌃a:

and then after typing ⌃k to kill the remaining text on the line, the shell prompt is deleted:

At this point, typing ls ⏎ has no effect. ⌃c, ⌃d or ⌃z also have no effect. It appears the shell is totally hung.

Discussion

This issue bears superficial similarity to #27 but is different:

• At least with version LibTerm version 5.1.4 (2), Nov 11, 2019 at 08:30, I do not have the issue described. For instance, if I type I can hit ← as many times as necessary to get to this point: and then can type very␣ to get: and now, if I press ⏎, I get: — note that the output includes long line, so pressing ⏎ mid-line did not truncate the remainder.
• This issue has to do with being able to edit the prompt text, not the command-line after the prompt.

[captain]

How are you even able to type a control character? There are no ctrl, tab, nor ARROW keys anywhere to be found on any of the virtual keyboards. This is the most critically missing feature I have seen so far. 😝