[Octave-bug-tracker] [bug #44661] The "pause" command with no parameter: strange behavior (GUI + Windows)

[Rik]

Follow-up Comment #4, bug #44661 (project octave):

There is something definitely wrong with the GUI and the terminal.  pause() is
supposed to be a character-oriented input and any key hit, not just <RETURN>,
should terminate the input.  However, on Windows it appears that the input is
line-buffered.  I can type a whole sentence after running pause() and it is
only when I hit <RETURN> that it is processed.

In the same vein, kbhit is supposed to return a single character and it too
waits until a <RETURN> is pressed.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44661>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/