Penguin
Recent Changes
Annotated edit history of dumpkeys(1) version 1 showing authors affecting page license. View with all changes included.
Rev Author # Line
1 perry 1 DUMPKEYS
2 !!!DUMPKEYS
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 FILES
8 SEE ALSO
9 ----
10 !!NAME
11
12
13 dumpkeys - dump keyboard translation tables
14 !!SYNOPSIS
15
16
17 __dumpkeys [[__ ''-hilfn1 -S''__shape__
18 ''-c''__charset__ ''--help --short-info --long-info
19 --numeric --full-table --separate-lines
20 --shape=''__shape__ ''--funcs-only --keys-only
21 --compose-only --charset=''__charset ]__
22 !!DESCRIPTION
23
24
25 __dumpkeys__ writes, to the standard output, the current
26 contents of the keyboard driver's translation tables, in the
27 format specified by keymaps(5).
28
29
30 Using the various options, the format of the output can be
31 controlled and also other information from the kernel and
32 the programs dumpkeys(1) and loadkeys(1) can
33 be obtained.
34 !!OPTIONS
35
36
37 ''-h --help''
38
39
40 Prints the program's version number and a short usage
41 message to the program's standard error output and
42 exits.
43
44
45 ''-i --short-info''
46
47
48 Prints some characteristics of the kernel's keyboard driver.
49 The items shown are:
50
51
52 Keycode range supported by the kernel:
53
54
55 This tells what values can be used after the __keycode__
56 keyword in keymap files. See keymaps(5) for more
57 information and the syntax of these files.
58
59
60 Number of actions bindable to a key:
61
62
63 This tells how many different actions a single key can
64 output using various modifier keys. If the value is 16 for
65 example, you can define up to 16 different actions to a key
66 combined with modifiers. When the value is 16, the kernel
67 probably knows about four modifier keys, which you can press
68 in different combinations with the key to access all the
69 bound actions.
70
71
72 Ranges of action codes supported by the kernel:
73
74
75 This item contains a list of action code ranges in
76 hexadecimal notation. These are the values that can be used
77 in the right hand side of a key definition, ie. the
78 ''vv'''s in a line
79
80
81 __keycode__ ''xx'' = ''vv vv vv vv''
82
83
84 (see keymaps(5) for more information about the format
85 of key definition lines). dumpkeys(1) and
86 loadkeys(1) support a symbolic notation, which is
87 preferable to the numeric one, as the action codes may vary
88 from kernel to kernel while the symbolic names usually
89 remain the same. However, the list of action code ranges can
90 be used to determine, if the kernel actually supports all
91 the symbols loadkeys(1) knows, or are there maybe
92 some actions supported by the kernel that have no symbolic
93 name in your loadkeys(1) program. To see this, you
94 compare the range list with the action symbol list, see
95 option ''--long-info'' below.
96
97
98 Number of function keys supported by kernel:
99
100
101 This tells the number of action codes that can be used to
102 output strings of characters. These action codes are
103 traditionally bound to the various function and editing keys
104 of the keyboard and are defined to send standard escape
105 sequences. However, you can redefine these to send common
106 command lines, email addresses or whatever you like.
107 Especially if the number of this item is greater than the
108 number of function and editing keys in your keyboard, you
109 may have some
110 loadkeys__(1) for more
111 details.
112
113
114 Function strings:
115
116
117 You can see you current function key definitions with the
118 command
119
120
121 __dumpkeys__''--funcs-only''
122
123
124 ''-l --long-info''
125
126
127 This option instructs __dumpkeys__ to print a long
128 information listing. The output is the same as with the
129 ''--short-info'' appended with the list of action symbols
130 supported by loadkeys(1) and dumpkeys(1),
131 along with the symbols' numeric values.
132
133
134 ''-n --numeric''
135
136
137 This option causes __dumpkeys__ to by-pass the conversion
138 of action code values to symbolic notation and to print the
139 in hexadecimal format instead.
140
141
142 ''-f --full-table''
143
144
145 This makes __dumpkeys__ skip all the short-hand
146 heuristics (see keymaps(5)) and output the key
147 bindings in the canonical form. First a keymaps line
148 describing the currently defined modifier combinations is
149 printed. Then for each key a row with a column for each
150 modifier combination is printed. For example, if the current
151 keymap in use uses seven modifiers, every row will have
152 seven action code columns. This format can be useful for
153 example to programs that post-process the output of
154 __dumpkeys__.
155
156
157 ''-1 --separate-lines''
158
159
160 This forces __dumpkeys__ to write one line per
161 (modifier,keycode) pair. It prefixes the word ''plain''
162 for plain keycodes.
163
164
165 ''-S --shape=''__shape__
166
167
168 Tells __dumpkeys__ to use the specified table shape.
169 Allowed shapes are __0__'':'' default shape (same as
170 no ''-S''); __1__: same as option ''--full-table'';
171 __2__: same as option ''--separate-lines''; __3__:
172 display one line per keycode (as in shape __1__), until
173 first hole is met, then use one line per (modifier,keycode)
174 pair (as in shape __2__).
175
176
177 ''--funcs-only''
178
179
180 When this option is given, __dumpkeys__ prints only the
181 function key string definitions. Normally __dumpkeys__
182 prints both the key bindings and the string
183 definitions.
184
185
186 ''--keys-only''
187
188
189 When this option is given, __dumpkeys__ prints only the
190 key bindings. Normally __dumpkeys__ prints both the key
191 bindings and the string definitions.
192
193
194 ''--compose-only''
195
196
197 When this option is given, __dumpkeys__ prints only the
198 compose key combinations. This option is available only if
199 your kernel has compose key support.
200
201
202 ''-c''__charset__
203 ''--charset=''__charset__
204
205
206 This instructs __dumpkeys__ to interpret character code
207 values according to the specified character set. This
208 affects only the translation of character code values to
209 symbolic names. Valid values for ''charset'' are listed
210 by the ''--help'' option. If no ''charset'' is
211 specified, __iso-8859-1__ is used as a default. This
212 option produces an output line `charset
213 __iso-8859-1__ but 0xba in
214 __iso-8859-8__).
215 !!FILES
216
217
218 ''/usr/share/keymaps/'' recommended directory for keymap
219 files
220 !!SEE ALSO
221
222
223 loadkeys(1), keymaps(5).
224 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.