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

[Mike Miller]

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

I haven't had a chance to test yet, but I was thinking more of a change like
this:


        m_interactive = (! is_octave_program && stdin_is_tty
                         && octave_isatty_wrapper (fileno (stdout)));

        // Not forced to be interactive if we're already interactive!
        if (m_interactive)
          m_app_context->forced_interactive (false);

        // Check if the user forced an interactive session.
        if (options.forced_interactive ())
          m_interactive = true;



The reason is because there are other parts of the code base that check for
similar conditions, and consider "forced_interactive" to mean that Octave
normally wouldn't have been interactive.

    _______________________________________________________

Reply to this item at:

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

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