[Octave-bug-tracker] [bug #55029] pause() with no arguments does not return like kbhit() with glibc 2.28

[INVALID.NOREPLY]

Follow-up Comment #70, bug #55029 (project octave):

So, actually I was using this behavior as a way to interact with octave-cli
via stdin/out. That is, I wrote a vscode debugger for octave which
communicates with the octave-cli process through stdin/out. Since the user
sends keyboard events to vscode, these are translated to stdin sequences.

I just confirmed on windows that version 5.2.0 when using pause requires an
keypress received directly by the octave-cli process to continue execution,
while version 5.1.0 can be unlocked via stdin.

Maybe we can find a halfway where we can set octave to one of two modes. stdio
mode (previous behavior) or a interactive mode (current behavior). That way I
could select the mode via some bool, and everyone is happy. How does that
sound?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55029>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/