|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #53635] CTRL-C does not work in all instances when using Windows GUI |
Date: | Tue, 17 Apr 2018 19:08:05 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #12, bug #53635 (project octave): This problem seems to be an interaction with the cmd.exe subprocess that is started when doing things like running makeinfo to format docstrings. I have a possible fix. The idea is to simply set the global interrupt state for the interpreter in terminal_dock_widget::terminal_interrupt instead of using Qt signals and slots and ultimately calling GenerateConsoleCtrlEvent (CTRL_C_EVENT, 0); to generate an interrupt. This approach works on my Debian system. Ctrl-C at the command prompt still works. I'll post a proper patch here after I have a chance to test it on Windows. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53635> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |