bugGNU Octave - Bugs: bug #53190, Can't get out of 'line' mode

 
 

bug #53190: Can't get out of 'line' mode

Submitter:  None
Submitted:  Tue 20 Feb 2018 08:29:48 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Mark D Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 4.0.3
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 20 Feb 2018 03:29:27 PM UTC, comment #2: 

It seems you just have more output than will fit on a single screen, and Octave is passing the result through the PAGER to help you wade through the data.

To confirm, open Octave and try


z = rand (1000, 1);


which will produce a thousand numbers in a column vector which should be more than will fit on one screen.

See the documentation on multi-page output: https://www.gnu.org/software/octave/doc/interpreter/Paging-Screen-Output.html

Simple solutions are to disable the pager entirely with 'more off' or configure the pager to behave as you like.



Rik <rik5>
Group administrator
Tue 20 Feb 2018 01:09:55 PM UTC, comment #1: 

Pressing 'q' exits the line mode.

Pressing Ctrl^C twice exits the line mode as well as octave with signal 2 (SIGINT), which of course, you won't want.

4.2.1 (latest stable release) instead lets you print the complete
 output on the cli without entering line mode.

Sahil <batterylow>
Tue 20 Feb 2018 08:29:48 AM UTC, original submission:  

I have been using the following code:


% ws_p08.m

a_c = [3, 4]
dx_c = [5, 12]
v0_c = [33, 56]/5

dx_p = comp2pol(dx_c)
Rx = [dx_c(1), dx_c(2); -dx_c(2), dx_c(1)]/dx_p(1)

v0_p = comp2pol(v0_c)
Rv0 = [v0_c(1), v0_c(2); -v0_c(2), v0_c(1)]/v0_p(1)

R = Rx' * Rv0

v_c = a_c * R * dx_p(1) / v0_p(1)

dx_o_c = [(v_c(1)^2 - v0_c(1)^2)/(2 * a_c(1)),(v_c(2)^2 - v0_c(2)^2)/(2 * a_c(2)) ]
dx_o_p = comp2pol(dx_o_c)



And



function c2p = comp2pol(cv)

   c2p = [(cv(1)^2 + cv(2)^2)^0.5, atand(cv(2)/cv(1))];


The code (ws_p08) runs, but I get into a mode where it tells me what line I’m at.  Once in that mode I don’t know how to get out of it.  I can’t even close Octave through normal means (This is what I consider an unambiguous bug.  The rest could be my ignorance).  I’ve resorted to using a kill command to close Octave when this occurs.

I am using the Octave GUI.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by batterylow (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-02-20 rik5 Item GroupUnexpected Error or Warning None
        StatusNone Invalid / Not an Octave Bug
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code