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

[Mike Miller]

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

The intent of that change, in the commit log, seems to agree with me, if I'm
reading it right.

> Interactive means we are running a interactive session, forced interactive
means the interactive session needed to be forced.

Can we agree first on the intent? My preference would be that in a tty, when
Octave would be interactive anyway, "octave" and "octave --interactive" should
result in the same behavior. That's the way bash works as far as I can tell.

I've confirmed the following behavior differences when I run "octave
--interactive" in a tty environment:

* readline line editing is disabled
* readline setting blink_matching_paren is disabled
* more has no effect, pager is treated as disabled
* confirm_recursive_rmdir has no effect, treated as disabled
* scanf(..., "C") doesn't flush/consume an entire line from stdin

I think these should not be different, unless stdin is actually not a tty but
the "--interactive" option is used.

    _______________________________________________________

Reply to this item at:

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

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