Fix ctrl+p/ctrl+n navigation in multi-line TUI prompts #5473
+25
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Users can now navigate multi-line input with ctrl+p (up) and ctrl+n (down) without triggering history navigation. History only triggers when on the first line (ctrl+p) or last line (ctrl+n), matching standard Emacs and terminal behavior. Previously, ctrl+p/ctrl+n always triggered history navigation regardless of cursor position, making it impossible to edit multi-line input with Emacs-style keybindings.
Corrected import path for solid-plugin to resolve TypeScript error that was blocking pre-push hooks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary