[Octave-bug-tracker] [bug #60079] (Windows) Ctrl-C / Ctrl-V dysfunctional in Command Window

[Philip Nienhuis]

Follow-up Comment #19, bug #60079 (project octave):

In dev Octave on my Linux box, disabling global shortcuts when the command
window has focus also disables interrupting commands with Ctrl-c.

So this (Crtl-c no more interrupting commands) actually looks like a
regression.
The other issue, that the setting has no effect in the 6.x branch (and
possibly before) has silently been "fixed"; I'd agree to leave it as-is for
the stable branch, as about nobody seems to have noticed it.

BTW I didn't even try interrupting e.g., a 'pause(10)' but rather entered
rubbish w/o pressing Enter, and then pressed Ctrl-c. If Octave ignores the
input and returns to the prompt I'd call it "interrupting commands".
It is that scenario (not being able to simply ignore commands that were
accidentally input by e.g., arrow up and inadvertent editing etc.) that is
most annoying to me. There may be a readline command but most Windows users
would be ignorant of that.

    _______________________________________________________

Reply to this item at:

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

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