nonblocking read-key
Posted: Mon Dec 10, 2018 5:02 am
I'm glad for the new non-blocking option for read-key (read-key true).
Lutz, is it intentional that (read-key true) returns 0 instead of nil when there is no keypress to report?
Lutz, is it intentional that (read-key true) returns 0 instead of nil when there is no keypress to report?