> This is not a bug of Sawfish, but because xkb's binding has indeed changed.
I disagree: XKB's bindings have not changed such that Shift+Backspace
maps to Terminate_Server. This can be confirmed with xev(1):
KeyRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x23d, subw 0x0, time 1568583639, (315,490), root:(341,547),
state 0x11, keycode 22 (keysym 0xff08, BackSpace), same_screen YES,
XLookupString gives 1 bytes: (08) "
XFilterEvent returns: False
(state 0x11 = NumLock + Shift). From /usr/share/X11/xkb/symbols/terminate:
key <BKSP> {
type="CTRL+ALT",
symbols[Group1] = [ NoSymbol, Terminate_Server ]
};
And /usr/share/X11/xkb/types/pc:
type "CTRL+ALT" {
modifiers = Control+Alt;
map[Control+Alt] = Level2;
level_name[Level1] = "Base";
level_name[Level2] = "Ctrl+Alt";
};
So <BKSP> is made a special type of key, where Level2 is reached by
Ctrl+Alt instead of by Shift (or by Shift or Caps Lock). I believe
sawfish is incorrectly interpreting the key sequence by assuming that
Level2 means Shift, when for this key it does not. Further evidence
for this hypothesis: I see the same mistake for Shift+KP_Add and
Shift+KP_Subtract (misinterpreted by sawfish as XF86_Next_VMode and
XF86_Prev_VMode, respectively).
--
Tim Bagot, BlueArc Engineering
