1DUMPKEYS(1) General Commands Manual DUMPKEYS(1)
2
6 dumpkeys - dump keyboard translation tables
7
9 dumpkeys [ -hilfn -ccharset --help --short-info --long-info --numeric
10 --full-table --funcs-only --keys-only --compose-only --charset=charset
11 ]
12
14 dumpkeys writes, to the standard output, the current contents of the
15 keyboard driver's translation tables, in the format specified by
16 keymaps(5).
17 Using the various options, the format of the output can be controlled
19 and also other information from the kernel and the programs dumpkeys(1)
20 and loadkeys(1) can be obtained.
21
23 -h --help
24 Prints the program's version number and a short usage message to
25 the program's standard error output and exits.
26 -i --short-info
28 Prints some characteristics of the kernel's keyboard driver. The
29 items shown are:
30 Keycode range supported by the kernel
32 This tells what values can be used after the keycode key‐
34 word in keytable files. See keymaps(5) for more informa‐
35 tion and the syntax of these files.
36 Number of actions bindable to a key
38 This tells how many different actions a single key can
40 output using various modifier keys. If the value is 16
41 for example, you can define up to 16 different actions to
42 a key combined with modifiers. When the value is 16, the
43 kernel probably knows about four modifier keys, which you
44 can press in different combinations with the key to
45 access all the bound actions.
46 Ranges of action codes supported by the kernel
48 This item contains a list of action code ranges in hexa‐
50 decimal notation. These are the values that can be used
51 in the right hand side of a key definition, ie. the vv's
52 in a line
53 keycode xx = vv vv vv vv
55 (see keymaps(5) for more information about the format of
57 key definition lines). dumpkeys(1) and loadkeys(1) sup‐
58 port a symbolic notation, which is preferable to the
59 numeric one, as the action codes may vary from kernel to
60 kernel while the symbolic names usually remain the same.
61 However, the list of action code ranges can be used to
62 determine, if the kernel actually supports all the sym‐
63 bols loadkeys(1) knows, or are there maybe some actions
64 supported by the kernel that have no symbolic name in
65 your loadkeys(1) program. To see this, you compare the
66 range list with the action symbol list, see option
67 --long-info below.
68 Number of function keys supported by kernel
70 This tells the number of action codes that can be used to
72 output strings of characters. These action codes are tra‐
73 ditionally bound to the various function and editing keys
74 of the keyboard and are defined to send standard escape
75 sequences. However, you can redefine these to send common
76 command lines, email addresses or whatever you like.
77 Especially if the number of this item is greater than the
78 number of function and editing keys in your keyboard, you
79 may have some "spare" action codes that you can bind to
80 AltGr-letter combinations, for example, to send some use‐
81 ful strings. See loadkeys(1) for more details.
82 Function strings
84 You can see you current function key definitions with the
86 command
87 dumpkeys --funcs-only
89 -l --long-info
91 This option instructs dumpkeys to print a long information list‐
92 ing. The output is the same as with the --short-info appended
93 with the list of action symbols supported by loadkeys(1) and
94 dumpkeys(1), along with the symbols' numeric values.
95 -n --numeric
97 This option causes dumpkeys to by-pass the conversion of action
98 code values to symbolic notation and to print the in hexadecimal
99 format instead.
100 -f --full-table
102 This makes dumpkeys skip all the short-hand heuristics (see
103 keymaps(5)) and output the key bindings in the canonical form.
104 First a keymaps line describing the currently defined modifier
105 combinations is printed. Then for each key a row with a column
106 for each modifier combination is printed. For example, if the
107 current keymap in use uses seven modifiers, every row will have
108 seven action code columns. This format can be useful for example
109 to programs that post-process the output of dumpkeys.
110 --funcs-only
112 When this option is given, dumpkeys prints only the function key
113 string definitions. Normally dumpkeys prints both the key bind‐
114 ings and the string definitions.
115 --keys-only
117 When this option is given, dumpkeys prints only the key bind‐
118 ings. Normally dumpkeys prints both the key bindings and the
119 string definitions.
120 --compose-only
122 When this option is given, dumpkeys prints only the compose key
123 combinations. This option is available only if your kernel has
124 compose key support.
125 -ccharset --charset=charset
127 This instructs dumpkeys to interpret character code values
128 according to the specified character set. This affects only the
129 translation of character code values to symbolic names. Valid
130 values for charset currently are iso-8859-X, Where X is a digit
131 in 1-9. If no charset is specified, iso-8859-1 is used as a
132 default. This option produces an output line `charset
133 "iso-8859-X"', telling loadkeys how to interpret the keymap.
134 (For example, "division" is 0xf7 in iso-8859-1 but 0xba in
135 iso-8859-8.)
136
138 /lib/kbd/keymaps recommended directory for keytable files
139
141 loadkeys(1), keymaps(5)
142 1 Sep 1993 DUMPKEYS(1)