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

[Mike Miller]

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

As an example:


$ rlwrap -C myprogram octave --eval 'a = input ("enter something>> ", "s")'
enter something>> first
$ rlwrap -C myprogram octave --eval 'a = input ("enter something>> ", "s")'
enter something>> second



If you call Octave this way, you get your own custom readline wrapper around
Octave, your own history file (~/.myprogram_history by default), you can
configure your own command completions if you want, and so on. IMHO this is
much better done outside of Octave, if I'm understanding correctly what you're
trying to do.

    _______________________________________________________

Reply to this item at:

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

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