|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #37672] GUI doesn't react to CTRL+C |
Date: | Thu, 14 Nov 2013 06:03:21 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130917 Firefox/17.0 Iceweasel/17.0.9 |
Follow-up Comment #30, bug #37672 (project octave): The idea is for --no-gui-libs to bring up a command-line only version of Octave in which graphics and any graphical user interface elements might not even work. The --no-gui option should start Octave in a command-line mode that still allows graphics and ui* functions to work. But currently the --no-gui thing is not really working, so I'm beginning to think that we should just make --no-gui mean the same as --no-gui-libs for the 3.8 release. Then interrupt handling is solved for those two cases. It also looks like the pthread_kill/pthread_sigmask thing works for the GUI in Unix systems. Then we are just left with making interrupts work properly for Windows systems. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?37672> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |