[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53034] Octave GUI fails to open when stdin cl

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #53034] Octave GUI fails to open when stdin closed. Patch included
Date: Thu, 1 Feb 2018 12:30:22 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0

Update of bug #53034 (project octave):

                  Status:                    None => Patch Submitted        


Follow-up Comment #1:

I also glanced at the forum discussion last week. I have no problem with the
proposed change, but I doubt it will fix anything for a great number of

I assume you are referring to the GLib g_spawn family of functions? In
particular, those functions set stdin to /dev/null by default, unless the
users chooses for the child to inherit stdin or to receive a fifo as stdin. I
assume most window managers and desktop environments execute launchers with
stdin set to /dev/null, which will still be considered by Octave to be an
empty file input, not a closed file descriptor. But I have not tested every
windowing environment to verify this.

The surest solution is to continue to use --force-gui when intending to run
Octave's GUI.

But like I said at the start, I have no problem with the proposed change. The
only way I know how to test whether this change will work is to run

$ octave             ## start GUI, stdin is a tty
$ octave <&-         ## start GUI, stdin is closed
$ octave </dev/null  ## exit with success, stdin is empty file


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]