|
| From: | John W. Eaton |
| Subject: | [Octave-bug-tracker] [bug #53635] CTRL-C does not work in all instances when using Windows GUI |
| Date: | Wed, 18 Apr 2018 09:31:13 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #16, bug #53635 (project octave):
Not mentioned here yet is bug #45654. My first patch alone would have fixed
that problem, but sometimes people do want Ctrl-C at the command prompt to
interrupt subprocesses. So I don't know exactly what to do about these
issues. We probably do need a way to allow a processes to be started in a
separate process group, then that feature can be used to open external editor
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] |