Changes between Version 1 and Version 2 of Ticket #4632, comment 5
- Timestamp:
- 01/18/25 19:58:49 (5 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4632, comment 5
v1 v2 31 31 * FreeBSD and Solaris consoles are already doing the right thing (magically?) 32 32 33 {{{ 34 keycode 59 = F1 F11 Console_13 35 keycode 60 = F2 F12 Console_14 36 keycode 61 = F3 F13 Console_15 37 ... 38 }}} 39 33 40 Source: https://github.com/torvalds/linux/blob/master/drivers/tty/vt/defkeymap.map 34 41 42 {{{ 43 # Old keyboards have 10 function keys, and keymaps have 44 # sometimes used shift+F1 = F11, and sometimes shift+F1 = F13. 45 # Here we assume an enhanced keyboard (with 12 function keys). 46 # 47 plain keycode 59 = F1 48 plain keycode 60 = F2 49 plain keycode 61 = F3 50 ... 51 shift keycode 59 = F13 52 shift keycode 60 = F14 53 shift keycode 61 = F15 54 }}} 55 56 Source: https://github.com/legionus/kbd/blob/master/data/keymaps/i386/include/linux-keys-bare.inc#L17 57 35 58 So maybe we can just fix it, at least for physical consoles, or am I being naive? We won't get around physical F11/F12 producing different sequences from Shift-F1 and Shift-F2. There will still confusion remaining as to how key bindings are working and people will wonder why no action can be bound to physcial F11/F12 (unless we implement them under a different name like `pf11, pf12, pf21, pf22`). But overall, a very long-standing problem will be solved for a lot of users.
