Arrow Up Down Nav fix#915
Merged
dgageot merged 1 commit intodocker:mainfrom Nov 24, 2025
Merged
Conversation
Signed-off-by: Jean-Laurent de Morlhon <jeanlaurent@morlhon.net>
dgageot
approved these changes
Nov 24, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix TUI input editor history navigation
The up/down arrow keys now properly distinguish between history-loaded
content and user-typed content. When a user manually types text, the
arrows navigate the cursor within that text instead of replacing it
with history entries.
Behavior:
This prevents accidentally losing typed content when pressing arrow keys.
Which happened a lot, especially now we got shift-enter for new line