1XKBEVD(1) General Commands Manual XKBEVD(1)
2
6 xkbevd - XKB event daemon
7
9 xkbevd [ options ]
10
12 This command is very raw and is therefore only partially implemented;
13 we present it here as a rough prototype for developers, not as a gen‐
14 eral purpose tool for end users. Something like this might make a
15 suitable replacement for xev; I'm not signing up, mind you, but it's
16 an interesting idea.
17 The xkbevd event daemon listens for specified XKB events and executes
19 requested commands if they occur. The configuration file consists of
20 a list of event specification/action pairs and/or variable definitions.
21 An event specification consists of a short XKB event name followed by a
23 string or identifier which serves as a qualifier in parentheses; empty
24 parenthesis indicate no qualification and serve to specify the default
25 command which is applied to events which do not match any of the other
26 specifications. The interpretation of the qualifier depends on the
27 type of the event: Bell events match using the name of the bell, mes‐
28 sage events match on the contents of the message string and slow key
29 events accept any of press, release, accept, or reject. No other
30 events are currently recognized.
31 An action consists of an optional keyword followed by an optional
33 string argument. Currently, xkbev recognizes the actions: none,
34 ignore, echo, printEvent, sound, and shell. If the action is not spec‐
35 ified, the string is taken as the name of a sound file to be played
36 unless it begins with an exclamation point, in which case it is taken
37 as a shell command.
38 Variable definitions in the argument string are expanded with fields
40 from the event in question before the argument string is passed to the
41 action processor. The general syntax for a variable is either $cP or
42 $(str), where c is a single character and str is a string of arbitrary
43 length. All parameters have both single-character and long names.
44 The list of recognized parameters varies from event to event and is too
46 long to list here right now. This is a developer release anyway, so
47 you can be expected to look at the source code (evargs.c is of particu‐
48 lar interest).
49 The ignore, echo, printEvent, sound,and shell actions do what you would
51 expect commands named ignore, echo, printEvent, sound, and shell to do,
52 except that the sound command has only been implemented and tested for
53 SGI machines. It launches an external program right now, so it should
54 be pretty easy to adapt, especially if you like audio cues that arrive
55 about a half-second after you expect them.
56 The only currently recognized variables are soundDirectory and sound‐
58 Cmd. I'm sure you can figure out what they do.
59
61 -help Prints a usage message that is far more up-to-date than any‐
62 thing in this man page.
63 -cfg file
65 Specifies the configuration file to read. If no configuration
66 file is specified, xkbevd looks for ~/.xkb/xkbevd.cf and $(LIB‐
67 DIR)/xkb/xkbevd.cf in that order.
68 -sc cmd Specifies the command used to play sounds.
70 -sd directory
72 Specifies a top-level directory for sound files.
73 -display display
75 Specifies the display to use. If not present, xkbevd uses
76 $DISPLAY.
77 -bg Tells xkbevd to fork itself (and run in the background).
79 -synch Forces synchronization of all X requests. Slow.
81 -v Print more information, including debugging messages. Multi‐
83 ple specifications of -v cause more output, to a point.
84
86 X(7)
87
89 Copyright 1995, Silicon Graphics Computer Systems Copyright 1995, 1998
90 The Open Group
91 See X(7) for a full statement of rights and permissions.
92
94 Erik Fortune, Silicon Graphics
95X Version 11 xkbevd 1.1.1 XKBEVD(1)