[Octave-bug-tracker] [bug #53034] Octave GUI fails to open when stdin closed. Patch included

[Mike Miller]

Follow-up Comment #14, bug #53034 (project octave):

Yes, I think that is a decent summary, thanks jwe.

We have had additional discussion over on the Arch forums, and I would venture
to say we've had a slight breakthrough in communications. I have been able to
explain that we want octave to behave primarily as a command interpreter, with
behavior similar to the bash or python interpreters.

If octave can somehow determine that the user intends to run octave
"interactively", whatever that means, then octave should start a REPL (which
may be a GUI-based REPL). So far the only way we have to test for implicit
interactivity is to check that stdin is a terminal.

Now that octave has included a GUI for a few releases, we can certainly
revisit and have a discussion on

* what the default behavior should be in different execution environments,
* whether the 'octave-gui' executable should be in PATH or obscured as it is
now,
* whether 'octave --force-gui' is better or worse than a separate 'octave-gui'
command,
* whether the GUI should become the implicit default and we should introduce a
new command or command-line option for batch processing,
* and so on.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53034>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/