Hi Branden, > Consequently, a user of a curses application that employs keypad > mode may experience a pause or “hang” after pressing the escape key > while curses collects sufficient characters to disambiguate the > input. If the window is in “no time‐out” mode, the escape delay is > effectively infinite; see notimeout(3NCURSES). In the event of > such a pause, further typing “awakens” curses.
After reading your explanation I spent a bit of time debugging and tracing the execution. It took me a while, but eventually I realized that the infinite loop was in kgetch(), caused by my driver. There was a bug that made it wait in a loop inside of read(). It was indeed waiting for more characters to disambiguate between different escape sequences... With this I've managed to get the keyboard working just fine, thanks for all the help! Regards, Antonio
