Timon

Related to old issue: https://github.com/crossterm-rs/crossterm/issues/38 it is very strange behavior and probably has to with the order in which rust invokes the Display implemented for tose types and then how...

The problem arises when you print at the same line. If you set style, print a string without line break and then set the style back, and then flush you...

It sounds like a nice idea, some kind of queue guard that always flushes automatically at some adjustable setting. BufWrite also does something similar tough, it is customized for the...

The github actions you are running crossterm in, isn't a real terminal and crossterm can not read key events from that. I forgot the exact reason of this panic, but...

I understand the concern, having a result here seems logical, while it might be a little less inconvenient for the majority of the application where this event-reader is always set....

No that is a good solution, I was thinking of that as well. We can mimic the behavior of output, input, error streams.

Maybe something as described here could be implemented: https://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html# And just a simple boolean to indicate a press/release in `KeyEvent`: https://github.com/crossterm-rs/crossterm/blob/master/src/event.rs#L390

Renaming the issue, since windows does mouse-up event support.

Crossterm supports interrupting the read. Though it can currently only be accessed from the internal code. This waker was implemented for asynchronous behavior. The asynchronous code uses a type called...

Crossterm allows you to poll for event readiness with `poll`. This can be used in combination with `read` to prevent read from blocking. Alternatively, you can set up a loop...