feat(tui) normalize vim-style navigation across forms and overlays#188
Merged
Conversation
…rrectly in tests.rs
Resolve Usage Query TUI conflicts and keep j/k field navigation aligned with arrow-key behavior.
Owner
|
LGTM, THANKS |
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.
Follow-up to #183.
This extends vim-style navigation handling across TUI forms and overlays by normalizing
hjklat the main key-entry point when no text input is active, while preserving literalhjklinput in editing contexts.Changes:
hjklas navigation only when text input/editor/filter/form editing is inactivej/khandling from individual form handlers