[Octave-bug-tracker] [bug #53412] KBHIT does not detect anything from command line, nor does it error out.

[John W. Eaton]

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

I think the purpose of that check was to avoid trouble if Octave was reading a
script from stdin.  But if Octave is invoked with


octave script.m  ## [1]


instead of something like


octave < script.m  ## [2]


or


cat script.m | octave  ## [3]


then I don't see why kbhit shouldn't work.  And, if I disable the check
entirely, currently Octave will work properly for [1] above, and [2] and [3]
will just return an empty string when kbhit is executed.

Even for something like


cat | octave


if I type kbhit<RET>, Octave will wait for input, accept a single character,
and continue.  So I don't see a good reason to keep the interactive check.

I pushed the following changeset on stable:

http://hg.savannah.gnu.org/hgweb/octave/rev/10ec5795bd06


    _______________________________________________________

Reply to this item at:

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

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