[Octave-bug-tracker] [bug #53635] CTRL-C does not work in Windows GUI

[Hartmut]

Follow-up Comment #6, bug #53635 (project octave):

Yes, I can now confirm that the result of pressing Ctrl-C in the command
window under Windows is somehow buggy compared to the behavior under Linux.
When running __run_test_suite__ from the command window:

* under Linux: Ctrl-C stops the execution pretty soon at any time

* under Windows (7, and also 10 if I remember right): It seems to me that the
execution can only be stopped when I press the Ctrl-C keys at a time BETWEEN
two consecutive tests (e.g. during the first 10 test cases in
__run_test_suite__). When I press Ctrl-C during a long running test (e.g.
bitfcns.cc-tst or bsxfun.cc-tst) then this does NOT stop the execution. Even
worse, this results in the freezing of the command windows, it just never
finishes this test then.

@Avinoam: Could you try to prepare a minimal test case for this Ctrl-C
behavior under Windows? (Currently our observations are a bit vague, this
probably makes it hard for other people to reproduce the problem.)

    _______________________________________________________

Reply to this item at:

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

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