pm100

BTW - if the answer is 'no' I am happy to hack away and see if I can do it

I only want it for the app I am writing (just like vim, nano,... that have also complained about the same thing) not globally. ie the app needs to turn...

no saying its slow just that its ugly to see the input/render cycle run twice for every key stroke. Rust is supposed to be super fast, hate to see cycles...

its just the samples. It cannot be fixed in general. I fixed the error in gitui (the project I am using textarea for, they had a much more serious issue,...

ah yes, so really key into should return Key::Skip or something to indicate that this input can be ignored.

I know how to deal with it in real life - I am a user of textarea in another project , the double keystrokes from crossterm were a huge issue....

I certainly think that ctrlz,ctrlx,ctrlc,ctrlv should be standard. And ctrla. I added ctrlc and ctrlx in the select PR BTW - I am working on a table lookup key dispatch...

Ctrlc does not always equal sigint . Raw mode passes it through as a plain ol keystroke. Interestingly this is bound to the other new issue about clipboard etc

It is up to the app author to decide what ctrlc should do. If they pass that keystroke to tta rather than acting on it themselves then doing a copy...

My 10cents The key dispatch logic in `input` should not be in tta. tta should be an API driven component, Many real uses require a complete replacement of that `input`...