Difference between revisions of "Tutorials/Keyboard"

Jump to: navigation, search
(Created page with "Keyboard actions are all actions that are triggered by the system when you do a keystroke. Most of them should be set by default so you are content. This article is here to help ...")
 
Line 1: Line 1:
 
Keyboard actions are all actions that are triggered by the system when you do a keystroke. Most of them should be set by default so you are content. This article is here to help you do your own settings. Most prominent examples are the "raise audio volume" and its siblings "lower audio volume" and "mute audio" on some multimedia keyboards.
 
Keyboard actions are all actions that are triggered by the system when you do a keystroke. Most of them should be set by default so you are content. This article is here to help you do your own settings. Most prominent examples are the "raise audio volume" and its siblings "lower audio volume" and "mute audio" on some multimedia keyboards.
 +
 +
= Background =
 +
When a key is pressed, this is sent as an electronic signal over the USB or PS/2 port to the computer. There it is received by the Linux kernel and forwarded to the X Windowing system. The X Windowing system receives the ''scancodes'' of the keys being pressed and maps them to key events, for example XF86audiomute. To change this mapping you have the xmodmap command. To see the scancodes that a keypress causes, you have the xev command. In short, when you press the "Audio Mute" button on your keyboard, the kernel receives the signal from the keyboard and sends a keycode, e.g. 121, to the X Windowing System. Using its xmodmap, the Windowing System emit the signal XF86AudioMute that can be received and handled e.g. by KDE.

Revision as of 10:13, 6 March 2011

Keyboard actions are all actions that are triggered by the system when you do a keystroke. Most of them should be set by default so you are content. This article is here to help you do your own settings. Most prominent examples are the "raise audio volume" and its siblings "lower audio volume" and "mute audio" on some multimedia keyboards.

Background

When a key is pressed, this is sent as an electronic signal over the USB or PS/2 port to the computer. There it is received by the Linux kernel and forwarded to the X Windowing system. The X Windowing system receives the scancodes of the keys being pressed and maps them to key events, for example XF86audiomute. To change this mapping you have the xmodmap command. To see the scancodes that a keypress causes, you have the xev command. In short, when you press the "Audio Mute" button on your keyboard, the kernel receives the signal from the keyboard and sends a keycode, e.g. 121, to the X Windowing System. Using its xmodmap, the Windowing System emit the signal XF86AudioMute that can be received and handled e.g. by KDE.


Content is available under Creative Commons License SA 4.0 unless otherwise noted.