You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use a feature that crossterm doesn't support directly, for example Kitty's graphics protocol, then the terminal will send escape sequences that crossterm doesn't understand.
In that case I would expect enum Event to have a UnrecognisedEscapeSequence(String) variant. However instead it seems to just report all of the characters in the escape sequence as Event::Key.
To reproduce, modify the event-read.rs example to send an image using the Kitty graphics protocol. You'll end up with something like this:
Note all the KeyEvents are really the terminal's confirmation that the image has been shown.
The text was updated successfully, but these errors were encountered:
If you use a feature that crossterm doesn't support directly, for example Kitty's graphics protocol, then the terminal will send escape sequences that crossterm doesn't understand.
In that case I would expect
enum Event
to have aUnrecognisedEscapeSequence(String)
variant. However instead it seems to just report all of the characters in the escape sequence asEvent::Key
.To reproduce, modify the
event-read.rs
example to send an image using the Kitty graphics protocol. You'll end up with something like this:Note all the
KeyEvent
s are really the terminal's confirmation that the image has been shown.The text was updated successfully, but these errors were encountered: