[Top][All Lists]

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

[Octave-bug-tracker] [bug #55819] Octave command number doesn't incremen

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55819] Octave command number doesn't increment after Ctrl+C
Date: Sun, 3 Mar 2019 13:05:59 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36

Update of bug #55819 (project octave):

                Category:                    None => Interpreter            
                Severity:              3 - Normal => 1 - Wish               
              Item Group:        Incorrect Result => Feature Request        
                  Status:                    None => Confirmed              
                 Summary: Octave line number doesn't advance after Cntrl-C
when resulting output => Octave command number doesn't increment after Ctrl+C


Follow-up Comment #1:

Confirmed with something simple like 'pause(10000)' and Ctrl+C.

Retitled to use the terminology used in liboctave. The number is the "command
number", and the interpreter only increments it when an expression is
evaluated and a return value is received. If the command is interrupted, there
is no return value, the 'ans' variable is also not updated, and the command
number is not incremented.

This is fairly low severity since most users (using the GUI) will see the '>>
' prompt, no command number.

I agree that this would be nice to fix. The bash shell for example does
increment its command number when the prompt contains '\#' and a command like
'sleep 1000' is interrupted.


Reply to this item at:


  Message sent via Savannah

reply via email to

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