[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: |
Wed, 27 Dec 2017 11:06:35 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 |
URL:
<http://savannah.gnu.org/bugs/?52750>
Summary: Ctl-C stops debugging when used only to stop long
output when more off
Project: GNU Octave
Submitted by: marsian
Submitted on: Wed 27 Dec 2017 04:06:34 PM UTC
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Assigned to: None
Originator Name: Marsian
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.2.1
Operating System: Microsoft Windows
_______________________________________________________
Details:
If I have 'more off', and then during debugging I run a command that displays
an excessive amount of effort, I am used to pressing ctl-c to stop the output
(I believe matlab does this). However besides only stopping the output to the
console, it also exits debugging mode. It should only stop the text output,
and not stop debugging (unless stopped at the command line and waiting?). I've
seen this in 4.2.1 and the dev version.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?52750>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #52750] Ctl-C stops debugging when used only to stop long output when more off,
Marshall <=