Summary: | Unconsistent keyboard shortcut to close konsole | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | erichnog |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | minor | CC: | adaptee, hr.denzler, nalvarez |
Priority: | NOR | ||
Version: | 2.5.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
erichnog
2010-10-14 03:32:25 UTC
Konsole has no control over the suspend/resume "shortcuts". They're implemented by the shell (eg. bash) or something even lower level. Same as Ctrl-C to send a SIGINT. Ctrl+D works also. /usr/share/doc/packages/bash/bashref.html --> delete-char (C-d) meaning EOF Consistency is important, but I don't think it is important enough for konsole to break app specific convention. Ctrl+Q is a longstanding convention, just like Ctrl+C. In konsole, Ctrl+C is not used as the shortcut of copying, should that inconsistency also be fixed? Is it worthwhile to write extra code to allow users to customize the shortcut of sending SIGINT so they can use Ctrl+C for copying and that customized shortcut for sending SIGINT? I don't think so. The same logic applies for Ctrl+Q. I will close it as WONTFIX. |