|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #44485] GUI: File | Exit from main menu doesn't work when Octave is busy |
Date: | Sun, 08 Mar 2015 17:34:42 +0000 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30 |
Follow-up Comment #5, bug #44485 (project octave): Another thing is that AFAIU the main menu's File | Exit instruction sequence is similar or equal to what the OS sends to Octave when e.g., shutting down. Indeed, when I enter: for ii=1:1000 eigs (randn (400)) endfor ...and try to shutdown the system I get a popup that program "Octave" is unresponsive. In far-fetched cases (say, laptop battery nearly exhausted) having Octave obstruct system actions is a bad idea; although I expect any OS to be able to simply ~"kill -9" Octave. So while I agree with Dan about consistent paths I think the main menu's File|Exit should have absolute priority over anything that happens in the terminal. It works that way when Octave is running in a rxvt or cmd32.exe terminal as well. A confirmation popup is a good idea. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?44485> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |