octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #44661] The "pause" command with no parameter:


From: Giorgio De Nunzio
Subject: [Octave-bug-tracker] [bug #44661] The "pause" command with no parameter: strange behavior (GUI + Windows)
Date: Mon, 30 Mar 2015 05:46:47 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36

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

I also checked the CLI version (that is, starting with octave.vbs --no-gui).
The behavior is *almost* identical.
Almost everything works the same: pause() returs only if I type <enter> and it
does not return after any other key, bufferizing them all (so that they are
taken by the following pause()s). 
The difference is that the <enter> key does not leave the LF bufferized, so
that the sequence: 
pause <enter> [command starts and waits]
<enter> [command exits as expected]
pause <enter> [command starts and waits, no LF bufferized]
<enter>  [command exits as expected]
works fine. But when you insert a <any other key>, pause() does not exit,
while the subsequent pause() exits immediately.
So for me the problem is not limited to the GUI: it is only the interpretation
of the <enter> key that is different.
Best
Giorgio
 

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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