[Octave-bug-tracker] [bug #60696] octave --interactive should not imply --no-line-editing when running in a terminal

[Rik]

Follow-up Comment #2, bug #60696 (project octave):

The code for this is in libinterp/corefcn/interpreter.cc.  Decision point is


        line_editing = options.line_editing ();
        if ((! m_interactive || options.forced_interactive ())
            && ! options.forced_line_editing ())
          line_editing = false;


Taking out "|| options.forced_interactive ()" is enough to make the logic work
the way we want.  The new line would be


        if (! m_interactive && ! options.forced_line_editing ())


Is there anything wrong with making this change?  If we are not operating from
a terminal and someone forces interactive do we just say it's their own fault
if things don't work out?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60696>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/