[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53412] KBHIT does not detect anything from co

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #53412] KBHIT does not detect anything from command line, nor does it error out.
Date: Wed, 25 Apr 2018 16:10:35 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

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]


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:



Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]