On Mon, May 13, 2013 at 7:11 PM, John W. Eaton <address@hidden
<mailto:address@hidden>> wrote:
On 05/06/2013 07:06 PM, Michael Goffioul wrote:
As a result of the change above, I suspect octave is not forked
anymore,
the terminal where you started it stays the controlling
terminal; hence
CTRL-C in that terminal as sent directly to octave as SIGINT. CTRL-O
does not correspond to any signal, so nothing happens.
Does CTRL-O work when you focus another widget than the embedded
terminal widget?
No, I don't think it was working properly.
Ben, what is the behavior on OS X systems? Do the keyboard
shortcuts work?
I can go back to forking and calling setsid on Unix systems and just
using the ioctl call on OS X.
At the very least, we should at least check the return value of ioctl.