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

[Mike Miller]

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

I just caught up on some additional comments on the Arch forum. I think the
most meaningful point is that it may be counter-intuitive that 'octave' only
automatically starts the GUI when it is run from a terminal, while it doesn't
start the GUI when it is not run from a terminal, which may be when some users
want the GUI most.

While octave is obviously not the only command interpreter to automatically
switch to an interactive REPL, and is also not the only program to
automatically switch between a graphical and a text-based mode, it may be one
of the only ones that tries to juggle all of those roles at once from a single
command. Maybe octave tries to be too clever for its own good.

One might pose the question: if most Octave GUI users must start it with
'octave --force-gui' from some kind of a launcher or menu, then what set of
users are served by starting the GUI automatically from 'octave' in a
terminal?

    _______________________________________________________

Reply to this item at:

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

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