[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: |
Sat, 29 May 2021 14:54:15 -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 |
URL:
<https://savannah.gnu.org/bugs/?60696>
Summary: octave --interactive should not imply
--no-line-editing when running in a terminal
Project: GNU Octave
Submitted by: mtmiller
Submitted on: Sat 29 May 2021 11:54:13 AM PDT
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Incorrect Result
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Release: dev
Discussion Lock: Any
Operating System: GNU/Linux
_______________________________________________________
Details:
In bug #60693, it's observed that 'octave -i' or 'octave --interactive'
disables readline line editing and history, even when run from a terminal.
This seems like a logic error in command line option parsing.
If running 'octave' in a terminal would enable readline line editing, then
'octave --interactive' in the same context should be the same. The only time
it should disable line editing is when '--interactive' is used and Octave
wouldn't have been running interactively otherwise.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60696>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #60696] octave --interactive should not imply --no-line-editing when running in a terminal,
Mike Miller <=