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

[Giorgio De Nunzio]

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

Here I am.

Gone to the windows line command (cmd) then 
cd C:OctaveOctave-4.0.0-rc2bin
(so I am using octave.exe as the starting executable)
then:

(1)  octave-cli
I launch test_pause.m by Rik, everything is ok, four <enter> key strokes, each
welcome by a number 1 to 4 
BUT keys different from <enter> don't make the pause finish: they are
bufferized and taken by the subsequent pause command.

(2) octave
the GUI opens, I launch test_pause.m: I need only two <enter> key strokes, and
numbers appear in pairs: after the first <enter> I see 1 then 2, after the
second <enter>, I see 3 then 4. Again, key strokes different from <enter>
don't oblige the pause to finish, and are bufferized for the future...

(3) octave --no-gui 
like (1)

(4) octave --no-gui-libs
like (1)

The automatically created Windows desktop start links to octave use octave.vbs
in
C:OctaveOctave-4.0.0-rc2
instead of directly calling the various octave executables in
C:OctaveOctave-4.0.0-rc2bin
but the results (as said in the previous messages) are alike.
Thanks
Best regards
Giorgio


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Messaggio inviato con/da Savannah
  http://savannah.gnu.org/