client-core: read an uppercase ASCII letter in a chord as the letter plus Shift #443
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis!443
Loading…
Reference in a new issue
No description provided.
Delete branch "client-core/uppercase-letter-chords"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A keymap chord written with an uppercase ASCII letter (
shift+A) parsed without a warning but could never match: the client lifts every uppercase keypress to the lowercase letter plus Shift, while the parser keptAas written. Per the decision on the issue (option 1), the parser now folds the same way.Chord::from_strreads a single uppercase ASCII letter as its lowercase letter plus SHIFT:A,shift+Aandshift+aare one chord. Unit tests and a proptest pin the fold.felis sessions send --keyparses with the same grammar, so its key event now sends Shift plus a letter as the uppercase keystroke with that letter composed, as a keyboard (and the GUI) does.--key Akeeps typingA, and--key shift+anow typesAinstead ofa.docs/reference/keybindings.mdchord grammar states the fold; CHANGELOG "Fixed" entries for the keymap and the CLI.Closes #386