getscancodes is very useful tool for grabbing scancodes. Quick howto for newbie
- install getscancodes from aur #yaourt -Sya getscancodes
- connect your device and recognize it #dmesg|tail -30
- find the event id of the device (use grep) #cat /proc/bus/input/devices
- run getscancodes #sudo getscancodes /dev/input/event18
I find that it easy just to use setkeycodes for a quick test # setkeycodes scancode keycode
- There's already a link to official instructions in Extra_Keyboard_Keys#See_also, so I'd say it's not necessary to add these to our wiki.
- setkeycodes and mapping with udev are described in Map_scancodes_to_keycodes, which is just fine - I don't know what you mean...
- Map_scancodes_to_keycodes and Extra_Keyboard_Keys are properly interlinked, and I'm against the merging at the moment because that would imply other pages should be merged too and the resulting page would be too long and hard to read.
- -- Lahwaacz (talk) 13:00, 21 October 2013 (UTC)
- Move Extra keyboard keys/Xorg to Xorg keyboard configuration#Keybinding. Can now be symlinked with new Xorg keybinding redirect.
- Move Extra keyboard keys/Console to Console keyboard configuration#Creating a custom keymap.
- Move Extra keyboard keys#In console to Console keyboard configuration#Identifying keycodes.
- Move Extra keyboard keys#In Xorg to Xorg keyboard configuration#Identifying keycodes.
- Moved scancode, keycode & keysym explanation, Identifying scancodes and Mapping scancodes to keycodes from Extra keyboard keys to Keyboard input.
- Renamed Map scancodes to keycodes to Scancode mapping with hwdb and moved
setkeycodesto Keyboard input.
- The whole point of announcing article rewrites in a talk page is to wait for replies and comments and not to go on with the proposal overnight. I really expected that a maintainer would comprehend this by himself, but apparently even constant reminders are not enough. Instead, you act like a bull in a china shop.
- I will review this over the weekend, let's see if you can wait with further changes at least if somebody asks. You still have the previous china shop to clean up.
- -- Lahwaacz (talk) 06:59, 1 June 2018 (UTC)
- Basically any of the moving you did did not improve anything:
- The description of modifying keymaps is scattered all over the Keyboard input page, Xorg keyboard configuration#Keybinding and Console keyboard configuration#Creating a custom keymap. This is exactly the same number as before (Extra keyboard keys, Extra keyboard keys in Xorg, Extra keyboard keys in console) but now it is mixed with the basic configuration only to confuse users and make the pages keyboard configuration pages more bloated. Even if the links between the current three pages were correct, you would have to start reading e.g. in Console keyboard configuration, then continue in Keyboard input to learn about scancodes etc. and finish again in Console keyboard configuration to modify a keymap. To avoid this, content should be grouped by topic, which the original state did much better than yours.
- The split of Map scancodes to keycodes to Keyboard input#Mapping scancodes to keycodes and Scancode mapping with hwdb does not make sense at all - Keyboard input#Mapping scancodes to keycodes contains the intro and a non-preferred method, while the preferred way has its own page. Again, the content should be grouped by topic.
- What's the purpose of Extra keyboard keys in your great plan? You left there the only thing which didn't fit into the original page (according to its introduction).
- As I don't find your restructuring better than the original state, I'll probably just start reverting it. Unless some influential people convince me otherwise. Not saying that the original state was ideal, but there was very little missing (like more descriptive titles).
- In any case, next time start the discussion before you start moving things around and, of course, wait for positive feedback.
- -- Lahwaacz (talk) 10:36, 3 June 2018 (UTC)
- Note: I've reverted the Keyboard input page (the last two points on your list). -- Lahwaacz (talk) 11:32, 3 June 2018 (UTC)
- It's ironic that you that you repeatedly remind me that content should be grouped by topic because that's exactly what I improved. The topic of scancodes, keycodes and keysyms is "keyboard input", not "extra keyboard keys". Describing keybinding under "extra keyboard keys" doesn't make any sense as you can bind any keys, not just special keys.--Larivact (talk) 12:24, 3 June 2018 (UTC)
- You moved "Identifying scancodes" to Keyboard input and "Identifying keycodes" to Console keyboard configuration and Xorg keyboard configuration so don't tell me anything about your great plan having sensible content grouping. We could have just discussed how to rename the Extra keyboard keys page and everybody would be happy. -- Lahwaacz (talk) 13:03, 3 June 2018 (UTC)
- Since binding special keys (or making some normal keys "special") is about the only thing for which knowing about scancodes, keycodes and keysyms is necessary, I don't see a point in describing these terms on a separate page. Even if you set up the wikilinks properly, I think it is much more sensible to keep it on one page rather than scattering the procedures which were laid out in Extra keyboard keys over multiple pages. As for a better title for Extra keyboard keys, you tell me... -- Lahwaacz (talk) 16:17, 3 June 2018 (UTC)
- So I just moved stuff back to Extra_keyboard_keys#Identifying_keycodes and flagged Keyboard_configuration_in_Xorg#Keybinding for merging with Keyboard shortcuts. I don't intend to restore the Extra keyboard keys/Console and Extra keyboard keys/Xorg subpages. -- Lahwaacz (talk) 09:02, 30 June 2018 (UTC)