[Octave-bug-tracker] [bug #37672] GUI doesn't react to CTRL+C

[John W. Eaton]

Follow-up Comment #24, bug #37672 (project octave):

Michael Godfrey:

What about the test with "kill -INT PID":

What happens if you execute "sleep (200)" at the Octave prompt and then do
"kill -INT PID" with PID == the process ID of the Octave process? This should
be the one that is shown as "octave" in the output from ps, not the
"lt-octave-gui" process. 

Does that deliver an interrupt signal to Octave?  If so, does it interrupt the
sleep function?

I'm trying to determine whether it is a problem with Ctrl-C not being acted on
by Qt (we expect that it is defined as a keyboard shortcut that will
eventually put us in the copyClipboard function in the terminal widget) or if
it is that signal handling is not working.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?37672>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/