[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #37078] GUI mode should automatically fall bac
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #37078] GUI mode should automatically fall back to CLI mode if no X server |
Date: |
Sat, 11 Aug 2012 21:44:27 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.75 Safari/537.1 |
URL:
<http://savannah.gnu.org/bugs/?37078>
Summary: GUI mode should automatically fall back to CLI mode
if no X server
Project: GNU Octave
Submitted by: mtmiller
Submitted on: Sat 11 Aug 2012 05:44:27 PM EDT
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Feature Request
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
The newly unified octave+gui executable exits with an error if it cannot
connect to X or if DISPLAY is unset, e.g. over SSH without X forwarded.
warning: X11 DISPLAY environment variable not set
octave: cannot connect to X server
The error is internal to Qt and I don't think there's a way to detect the
condition, Qt just exits immediately (*love* it when library code chooses to
exit for me).
Ideally, if the user runs octave without specifying --force-gui or --no-gui,
it should detect whether it can connect to X first, and fall back to CLI mode
if not. Currently, user has to read the error, know what it means, and run
octave --no-gui.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?37078>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #37078] GUI mode should automatically fall back to CLI mode if no X server,
Mike Miller <=