REPL: Fix Ctrl-A behavior after multiline history recall #60838
+19
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After recalling a multiline history entry,
key_repeatscould remain non-zero,causing Ctrl-A to be interpreted as a repeated key press. This resulted in the
cursor jumping to the start of the entire input on first Ctrl-A.
This change ensures that:
Ctrl-A once moves to the start of the current line
Repeated Ctrl-A still moves to the start of the input
#AI tools were used to assist with code exploration and reasoning; all changes were implemented and verified manually.
Fixes #60779