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

[John W. Eaton]

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

Taking a step back, I think maybe we should define what we want to do.  As I
understand it, we'd like to have octave start "from window manager launchers"
(whatever that means) and also we want to be able to execute any of the
following at a shell prompt and have them work as described:


## Read command from named file:
octave FILE

## Read commands from stdin, redirected from a file:
octave < FILE

## Read commands from a pipe:
echo "some commands" | octave

## Start Octave interactively, reading input from a terminal:
octave


The check on "isatty (stdin)" works perfectly well to distinguish reading
stdin redirected from a file or from a pipe vs reading commands interactively
from a terminal, at least in the cases shown above.

As I understand it, Mike is saying that the way some window manager launchers
start programs like Octave is indistinguishable  from one or more of the
above, at least using methods we know about.  So what can we do to detect the
case of Octave being started by some window manager launcher?  It must also
allow all of the ways of running Octave shell commands to continue to work. 
If it's possible to do that, then we can eliminate the --force-gui option. 
Otherwise, I think we are stuck with it, because we are not going to give up
the ability to run commands as above.

Or, am I misunderstanding the issues here?

Finally, there's no need to be rude.  Telling (whether explicitly, or
implicitly by your rudeness) that you think we are idiots is not going to help
fix the problem.

    _______________________________________________________

Reply to this item at:

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

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