Differences between current version and predecessor to the previous major change of keymaps(5).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 2 | Last edited on Tuesday, June 4, 2002 12:30:38 am | by perry | |
Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:30:38 am | by perry | Revert |
@@ -105,9 +105,9 @@
Which of the actions bound to a given key is taken when it
is pressed depends on what modifiers are in effect at that
moment. The keyboard driver supports 8 modifiers. These
-modifiers are labeled (completely arbitrarily) Shift, AltGr,
+modifiers are labeled (completely arbitrarily) Shift, !
AltGr,
Control, Alt, ShiftL, ShiftR, CtrlL and CtrlR. Each of these
modifiers has an associated weight of power of two according
to the following table:
@@ -117,9 +117,9 @@
Shift 1
-AltGr 2
+!
AltGr 2
Control 4
@@ -152,24 +152,24 @@
achieved by binding appropriate key actions to desired keys.
For example, binding the symbol Shift to a key sets the
Shift modifier in effect when that key is pressed and
cancels the effect of that modifier when the key is
-released. Binding AltGr_Lock to a key sets AltGr in effect
+released. Binding !
AltGr_Lock to a key sets !
AltGr in effect
when the key is pressed and cancels the effect when the key
-is pressed again. (By default Shift, AltGr, Control and Alt
-are bound to the keys that bear a similar label; AltGr may
+is pressed again. (By default Shift, !
AltGr, Control and Alt
+are bound to the keys that bear a similar label; !
AltGr may
denote the right Alt key.)
Note that you should be very careful when binding the
modifier keys, otherwise you can end up with an unusable
keyboard mapping. If you for example define a key to have
Control in its first column and leave the rest of the
-columns to be VoidSymbols, you're in trouble. This is
+columns to be !
VoidSymbols, you're in trouble. This is
because pressing the key puts Control modifier in effect and
the following actions are looked up from the fifth column
(see the table above). So, when you release the key, the
-action from the fifth column is taken. It has VoidSymbol in
+action from the fifth column is taken. It has !
VoidSymbol in
it, so nothing happens. This means that the Control modifier
is still in effect, although you have released the key.
Re-pressing and releasing the key has no effect. To avoid
this, you should always define all the columns to have the
@@ -210,21 +210,21 @@
to indicate that the lines of the keymap will not specify
all 256 columns, but only the indicated ones. (In the
-example: only the plain, Shift, AltGr, Control,
+example: only the plain, Shift, !
AltGr, Control,
Control+Shift, Alt and Control+Alt maps, that is, 7 columns
instead of 256.) When no such line is given, the keymaps 0-M
will be defined, where M+1 is the maximum number of entries
found in any definition line.
-Next, you can leave off any trailing VoidSymbol entries from
-a key definition line. VoidSymbol denotes a keyboard action
+Next, you can leave off any trailing !
VoidSymbol entries from
+a key definition line. !
VoidSymbol denotes a keyboard action
which produces no output and has no other effects either.
For example, to define key number 30 to output 'a'
unshifted, 'A' when pressed with Shift and do nothing when
-pressed with AltGr or other modifiers, you can
+pressed with !
AltGr or other modifiers, you can
write
__keycode__ ''30'' __=__ ''a A''
@@ -232,10 +232,10 @@
instead of the more verbose
-keycode 30 = a A VoidSymbol VoidSymbol \
-VoidSymbol VoidSymbol VoidSymbol ...
+keycode 30 = a A !
VoidSymbol !
VoidSymbol \
+!
VoidSymbol !
VoidSymbol !
VoidSymbol ...
For added convenience, you can usually get off with still
more terse definitions. If you enter a key definition line
@@ -261,12 +261,12 @@
Shift X y
-AltGr x Y
+!
AltGr x Y
-Shift+AltGr X y
+Shift+!
AltGr X y
Control Control_x Control_y
@@ -276,15 +276,15 @@
Control_x Control_y
-AltGr+Control
+!
AltGr+Control
Control_x Control_y
-Shift+AltGr+Control
+Shift+!
AltGr+Control
Control_x Control_y
@@ -294,12 +294,12 @@
Shift+Alt Meta_X Meta_y
-AltGr+Alt Meta_x Meta_Y
+!
AltGr+Alt Meta_x Meta_Y
-Shift+AltGr+Alt
+Shift+!
AltGr+Alt
Meta_X Meta_y
@@ -312,15 +312,15 @@
Meta_Control_x Meta_Control_y
-AltGr+Control+Alt
+!
AltGr+Control+Alt
Meta_Control_x Meta_Control_y
-Shift+AltGr+Control+Alt
+Shift+!
AltGr+Control+Alt
Meta_Control_x Meta_Control_y
!!SINGLE MODIFIER DEFINITIONS
@@ -332,9 +332,9 @@
not. There is, however, a variation of the definition syntax
for defining only single actions to a particular modifier
combination of a key. This is especially useful, if you load
a keymap which doesn't match your needs in only some
-modifier combinations, like AltGr+function keys. You can
+modifier combinations, like !
AltGr+function keys. You can
then make a small local file redefining only those modifier
combinations and loading it after the main file. The syntax
of this form is:
@@ -345,9 +345,9 @@
e.g.,
-plain keycode 14 = BackSpace
+plain keycode 14 = !
BackSpace
control alt keycode 83 = Boot
alt keycode 105 = Decr_Console
alt keycode 106 = Incr_Console
@@ -446,9 +446,9 @@
The following entry sets the Shift and Caps Lock keys to
behave more nicely, like in older typewriters. That is,
pressing Caps Lock key once or more sets the keyboard in
-CapsLock state and pressing either of the Shift keys
+!
CapsLock state and pressing either of the Shift keys
releases it.
keycode 42 = Uncaps_Shift