|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #60696] octave --interactive should not imply --no-line-editing when running in a terminal |
Date: | Tue, 1 Jun 2021 19:19:48 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36 |
Update of bug #60696 (project octave): Status: None => Confirmed _______________________________________________________ Follow-up Comment #1: That seems right. The '--interactive' should force Octave to behave as if was running in a normal terminal, even if it may not be. Starting in a terminal, I was able to force readline to work by adding the additional option '--line-editing' run-octave --interactive --line-editing This combination works just fine. _______________________________________________________ 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] |