docs: the power button, the maintenance chord, and why long-Escape should change

Records what was measured this pass and, as importantly, what was not. KGlobalAccel will accept a bare Escape and its component carries both a pressed and a released signal, so hold-and-cancel is expressible. What could not be measured here is whether a global shortcut takes the key away from applications, because key injection cannot reach the nested session. The mechanism says it does — KWin matches shortcuts in an input filter ahead of the focused surface — which would cost the classroom every ordinary use of Escape. That is inference, and it is written down as inference, with the thirty-second bench test that settles it. The recommendation is to change the gesture rather than grab the key an appliance uses most: hold-to-confirm on an on-screen control, which is ordinary Qt inside our own surface, or a modifier chord like the one the maintenance terminal just proved. Either keeps the deliberate ceremony without an input daemon. Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-10 15:24:28 -05:00
parent 30a924d945
commit 6050144e5d
6 changed files with 220 additions and 43 deletions
@@ -18,3 +18,12 @@ Terminal=false
 Categories=System;TerminalEmulator;
 NoDisplay=true
 StartupWMClass=org.kde.konsole
+# Konsole's own entry declares X-KDE-Shortcuts=Ctrl+Alt+T. That is a
+# chord a great many people know, and it is not one a classroom should
+# answer. Blanked here.
+X-KDE-Shortcuts=
+# Konsole's own entry also carries this, and it is what makes the default
+# chord inert even where the entry is still found: with the classroom's
+# shell_access=false the launch is refused. Measured — invoking that
+# shortcut over D-Bus opened nothing. Kept, so the two layers stay two.
+X-KDE-AuthorizeAction=shell_access