[Octave-bug-tracker] [bug #57220] Ctrl+C does not interrupt loops or demo sessions anymore

[John W. Eaton]

Follow-up Comment #4, bug #57220 (project octave):

If you remove the ~/.config/octave/octave-gui.ini file and restart Octave does
Ctrl-C work in the command window?

If I do that, Ctrl-C works.  But then if I go to the settings dialog and
uncheck the box for "Disable global shortcuts when Command Window has focus",
Ctrl-C stops working as the interrupt signal.  After that, selecting the
"Disable global shortcuts when Command Window has focus" checkbox doesn't seem
to restore the original behavior.

I tried comparing the octave-gui.ini file that was initially created to the
one that is saved after I start Octave and uncheck the "Disable global
shortcuts..." box but I don't see anything obvious and there are many
differences.  The fact that there are so many differences seems strange to me
since I only made one change to the settings during my session.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57220>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/