|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #51349] debug mode from a program has readline disabled |
Date: | Fri, 30 Jun 2017 17:22:57 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0 |
Update of bug #51349 (project octave): Priority: 5 - Normal => 3 - Low Status: None => Confirmed _______________________________________________________ Follow-up Comment #1: Confirmed. There is an easy enough workaround which is to start an interactive session of Octave and then run the script file to be debugged from the Command Window (GUI) or command line (CLI). The issue is that when running a script directly from the shell command line Octave believes it is being called in non-interactive batch mode. This would be common if you were running an already debugged script to analyze a new dataset. If Octave is running non-interactively, it believes it doesn't need line-editing capabilities supplied by Readline. Hence the behavior you are seeing. Another workaround would be to use the command-line option "--line-editing" which will force Octave to include Readline behavior. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?51349> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |