I think Ctrl-C behaving consistently in a Linux terminal, be it an actual terminal or a GUI-based one, is good behaviour. Ctrl-C for "copy" actually came a long time after Ctrl-C already had a meaning in a text terminal.
For that matter, how does Ctrl-C behave in Windows Command Prompt (if that's still how they call it)? In what way is it inconsistent: with the GUI or with the originating DOS terminal behaviour?
Mac went with Command and Control as separate keys on a keyboard, which avoids this particular issue, but it gets confusing quickly: what's a "command" and what's a "control"? Which key is to switch workspaces, and why is that "Control" and not "Command"? With every single shortcut, I wonder which was the one I need to use, and it's so hard to remember.
For that matter, how does Ctrl-C behave in Windows Command Prompt (if that's still how they call it)? In what way is it inconsistent: with the GUI or with the originating DOS terminal behaviour?
Mac went with Command and Control as separate keys on a keyboard, which avoids this particular issue, but it gets confusing quickly: what's a "command" and what's a "control"? Which key is to switch workspaces, and why is that "Control" and not "Command"? With every single shortcut, I wonder which was the one I need to use, and it's so hard to remember.
That's just poor UX.