Fix Alt+Shift+Char for crossterm backend #827
Open
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
Before this patch `cargo run --example key_codes --features crossterm-backend`:
AltChar('e')
Char('E')
After:
AltChar('e')
AltChar('E')
azat
added a commit
to azat/chdig
that referenced
this pull request
Jul 5, 2025
It turns out that crossterm supports ALT+CHAR, the problem was cursive, that does not handle ALT+SHIFT+CHAR, upstream fix [1], for now I will switch to patched version [1]: gyscos/cursive#827 But note, it is important to build with --release for normal performance.
Contributor
Author
|
Sorry, it has been incorrectly closed (because I mentioned this in my project), it still make sense |
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.
Before this patch
cargo run --example key_codes --features crossterm-backend:After: