[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #52750] Ctl-C stops debugging when used only t
|
From: |
Marshall |
|
Subject: |
[Octave-bug-tracker] [bug #52750] Ctl-C stops debugging when used only to stop long output when more off |
|
Date: |
Thu, 28 Dec 2017 16:02:49 -0500 (EST) |
|
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 |
Follow-up Comment #2, bug #52750 (project octave):
I would be OK with either pausing or skipping/stopping the text output. I only
really expect skipping/stopping text just as done at the command line when not
debugging.
Ctl-S and Ctl-Q didn't do anything in Windows. In Linux, Ctl-Q is assigned to
quit octave, and when it works has worse side effects, during debugging with
long text output, ctl-Q didn't do anything until after ctl-C stopped the text
output (and then it quit octave).
I tested in matlab, and Ctl-C works to stop the text output during debugging
without ending the debugging session.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?52750>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/