[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51658] fatal error does not leave Octave resu
|
From: |
Rik |
|
Subject: |
[Octave-bug-tracker] [bug #51658] fatal error does not leave Octave resulting in unresponsive command line |
|
Date: |
Sun, 3 Mar 2019 10:34:55 -0500 (EST) |
|
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Follow-up Comment #7, bug #51658 (project octave):
@Dan: Are you running the GUI or the CLI? Also, the original report mentioned
the pager, but the pager has been disabled by default now for some time ('more
off').
To test I used the CLI, but with Qt libraries linked in
run-octave -f
y = 1:1e6
<Ctrl+C>
I think the little bit of excess output you see on stdout is simply time lag
between typing <Ctrl+C> and having the interrupt routines fire. It doesn't
particularly bother me.
The original bug was about Octave becoming unresponsive which has been fixed.
You could file a new bug about updating the Octave history number after
command evaluation has finished, rather than after Octave has fully returned a
prompt to the user.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?51658>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/