|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #55029] pause() with no arguments does not return like kbhit() with glibc 2.28 |
Date: | Thu, 28 Mar 2019 18:26:43 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.75 Safari/537.36 |
Follow-up Comment #57, bug #55029 (project octave): Thanks for taking the effort to bring up a system to test this! You have already helped narrow this down even further, I had forgotten about the difference between the blocking 'kbhit ()' and the non-blocking 'kbhit (1)'. So I can confirm that 'kbhit (1)' causes 'kbhit ()' to stop waiting for input. But the first one does return a character if input is already waiting on stdin. I can reproduce this in earlier versions of Octave. Also, running octave --no-line-editing and calling 'kbhit(1)' causes Octave to exit immediately. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55029> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |