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

[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: Dan Sebald
Subject: [Octave-bug-tracker] [bug #51658] fatal error does not leave Octave resulting in unresponsive command line
Date: Sun, 3 Mar 2019 12:41:35 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Follow-up Comment #8, bug #51658 (project octave):

Regarding the lag.  I'm fine with the lag, but the odd part is the break in
the text.  There is a ^C followed by text that is discontinuous from the text
before the ^C.

I'm running CLI:


sebald@ ~ $ /usr/local/src/octave/octave/build1/run-octave
octave:1> more on
octave:2> y = 1:1e7


Here's what I'm seeing 


         29         30         31         32         33         34         35

 Columns 36 through 42:
warning: broken pipe


I find that strange, but this actually could be a pager issue on its own--I
suppose I should investigate the pager outside of Octave.

But I've just come across a bigger issue, which I think can be summed up as
"interrupting doesn't leave pager", which may be related to the original
issue.

Try the same bit of code:


octave:6> more on
octave:7> y = 1:1e7


and hit Cntrl-C somewhere when it is displaying:


 Columns 36 through 42:
-- less -- (f)orward, (b)ack, (q)uit


Octave is still in the pager, when maybe it shouldn't be.  Perhaps there is
some utility to being able to look at the output, even though the output isn't
complete.  However, the issue is that the pager can do something that requires
a Cntrl-C and _maybe_ the Cntrl-C no longer works in the pager?

While still in the pager, type <Shift>-F, which means to keep moving
(pressing) f indefinitely:


[snip]
 Columns 1259567 through 1259573:

    1259567    1259568    1259569    1259570    1259571    1259572    1259573

 Columns 1259574 through 1259580:

    1259574    1259575    1259576    1259577
Waiting for data... (interrupt to abort)


Cntrl-C doesn't work at this point.  (If there is a key sequence for abort, I
don't know it.)  So, at this point octave is hung.

Repeat the above sequence without pressing Cntrl-C (use y=1:1e6 if you like),
and Cntrl-C still works in the pager after having pressed <SHift>-F.

Anyway, it seems to me if Cntrl-C would also break out of the pager this
problem would be solved.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?51658>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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