[Octave-bug-tracker] [bug #51289] Up arrow not showing Octave history commands from an executable script

[John W. Eaton]

Follow-up Comment #1, bug #51289 (project octave):

Thanks for the report.

At some point, command-line editing was disabled when Octave is reading input
from a file.

You can force command-line editing to be enabled using --line-editing, but
unfortunately, there is no corresponding short option for that, and I think
most systems won't allow a #! line with -q --line-editing.

Instead of changing the default to have line editing enabled when Octave is
reading from scripts, I guess a better solution would be to enable line
editing just for functions that get user input, even when the main interpreter
loop is reading from a file.

I'll see if that's easy to do.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51289>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/