Nope, it is a crying shame the early Linux/Unix desktop environments copied the Windows/IBM CUA shortcuts and now we have to fight every app and every different method there is for setting keyboard shortcuts to fix it. The Ctrl key was already claimed for use in the terminal for signals and line navigation.
Toshy can help but it's still not a perfect fix.
> The Ctrl key was already claimed for use in the terminal for signals and line navigation.
First claim has no priority over better claim. Designs can and should improve
OK sure in general maybe, but that isn't what happened here. What happened is a worse design where Ctrl+C sometimes copies and sometimes kills the current process in your terminal. It's annoying and dumb and clearly inferior to what NeXTSTEP and macOS ended up doing with a separate "Super"/GUI/Command key to handle GUI shortcuts like Cut/Copy/Paste, and leaving Ctrl to handle UNIX shortcuts in the terminal. This allowed the readline/emacs text cursor navigation to also carry over into the GUI, so you can treat text anywhere the same regardless if its a GUI text editor or your terminal.