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

[Mike Miller]

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

On the other hand, I don't want input to add the text that was read to the
history list if I'm running Octave interactively.

This seems very wrong to me, but this is how it worked in Octave 3.6.4:


>> ls
>> pwd
>> ## Up and Down give me previous commands entered so far
>> text = input ("enter something>> ", "s")
enter something> ok
text = ok
>> ## now Up arrow gives me "ok" as if it were the previous command entered,
that's not good



That was fixed in 3.8.0. I don't think we want that behavior back by default.

For your use case, do you intentionally want to intermix Octave command
history and the history of what was entered into your custom input prompt?

If not, could you consider using rlwrap instead, which is an external program
that can wrap any program that gets input and automatically adds full readline
support, including history and command editing?

    _______________________________________________________

Reply to this item at:

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

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