octave-bug-tracker
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60696] octave --interactive should not imply

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #60696] octave --interactive should not imply --no-line-editing when running in a terminal
Date: Thu, 3 Jun 2021 20:30:08 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36 
Follow-up Comment #8, bug #60696 (project octave):

I traced this change in behavior to the fix for bug #48620
(https://hg.savannah.gnu.org/hgweb/octave/rev/a032ffb80704), which was first
released with version 4.2.0. In this change, the logic was dropped to set
'forced_interactive' to false when Octave is already automatically
interactive. I think that was a mistake.

I can confirm that version 4.0.3 treats '--interactive' as a no-op when
running in a tty. And I can confirm that version 4.2.2 treats '--interactive'
the same way that current builds do.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/
reply via email to
[Prev in Thread] Current Thread [Next in Thread]