New answers tagged keyboard
It's not about how the keys are represented by the "terminal" (i.e., the terminal emulator application). What you're seeing is the ANSI code (ANSI escape sequence) for the up arrow, translated into printable form. Keyboard hardware sends "scan codes", but they are translated and presented to commandline-level applications as characters. The key A becomes ...
Keyboards send events to the computer. An event says “scan code nnn down” or “scan code nnn up”. At the other end of the chain, applications running in a terminal expect input in the form of a sequence of characters. (Unless they've requested raw access, like the X server does.) When you press A, the keyboard sends the information “scan code 38 down”. The ...
This behavoir is different from shell to shell. Most shells use a library called readline to edit lines in the prompt. Here is a complete command reference for this library, so when an application is using readline you can edit and navigate the lines with this commands. The vertical arrow keys are configured in readline to navigate the command history. And ...
That's the way that the terminal represents the raw keycode of the Up key sent to it by the keyboard. Basically, your shell would normally intercept the keypress, but there's nothing to do that at the login prompt. So the character that you typed gets printed to the console just like any other letter (or number, or whatever).
Try this: setxkbmap -option keypad:pointerkeys and then the combination.
The keycodes are in [src]/drivers/tty/vt/defkeymap.map: # Default kernel keymap. This uses 7 modifier combinations. [...] See also my answer here for ways to view (dumpkeys) and modify (loadkeys) the current keymap as it exists in the running kernel. However, those are a bit higher level than the scancodes sent by the device. Those might be what's in ...
Try xmodmap, which is available in the x11-xserver-utils package in ubuntu. It allows you to remap any key combination.
On my laptop keyboard (Ubuntu 10.04) keyboard lock is currently On. $ xmodmap -pke|grep 77 keycode 77 = Num_Lock Pointer_EnableKeys Num_Lock Pointer_EnableKeys keycode 177 = XF86Phone NoSymbol XF86Phone $ xmodmap -e "keycode 77 =" Voila ! numlock is now disabled. xmodmap -e "keycode 77 = Num_Lock Pointer_EnableKeys Num_Lock Pointer_EnableKeys" Puts ...
Top 50 recent answers are included