xsconfig(X) X Version 11 (11 July 1990) xsconfig(X)
NAME
xsconfig - X configuration compiler
SYNOPSIS
xsconfig [-o configfile] sourcefile [. . . ]
DESCRIPTION
xsconfig is the configuration compiler you use to configure
the server. The server reads the file
/usr/lib/X11/.Xsight.cfg on start-up to set the initial
configuration. If the file $HOME/.Xsight.cfg exists, the
server reads it as the default.
If you do not specify an output configuration file with the
-o option, xsconfig writes xsight.cfg as the default
configuration file.
Multiple source files are processed in sequence.
A configuration source file is a text file that contains the
following lines:
+ A comment, if preceded by a semicolon.
+ A #include command that is a full path to another source
configuration file (full path is required since a search
strategy is not implemented). This command must have
the same syntax as the C preprocessor #include command.
+ A section header enclosed in square brackets, as
described in the following paragraphs.
+ Configuration settings or definitions in each section,
as described in the following paragraphs.
RESOURCES
Sections in a configuration file can be as follows:
[definitions]
This section contains definitions of the form:
#define name value
The name is a sequence of letters, numbers, and
underscores. Valid names are a superset of name values
in C preprocessor #define commands. Name must contain
at least one non-digit.
The value must be either a number sequence or a string
enclosed in quotation marks ("). There is currently no
use for string definitions. There is no expression
evaluator, so numeric values must be a single number
Page 1 (printed 7/3/90)
xsconfig(X) X Version 11 (11 July 1990) xsconfig(X)
using C conventions for specifying octal, decimal, and
hexadecimal numbers.
Any line in this section not beginning with #define is
interpreted as commentary.
The primary purpose of this section is to include the
file keysyms.h which defines the key symbol values.
You can find the definitions section in the config.txt
source file.
[Parameters]
This section contains various parameter settings of
the form:
parameter=value
The parameter is one of the names listed below.
The value must be a number or a symbol previously
defined in the definitions section.
ScreenWidth: This parameter specifies the physical
width of the screen in millimeters. There is no
useful default value if the parameter is unspecified.
ScreenHeight: The height of the screen in
millimeters. There is no useful default value if the
parameter is unspecified.
These values are calculated from the screen size you
specify during installation. You can find the
parameters section in config.txt.
[buttons]
This section specifies the mouse-button mapping. It is
a single line containing a list of numbers. The first
number is the logical button number for hardware button
1 and so on. On a three-button mouse, the middle button
is hardware button 2, and the left and right buttons are
1 and 3 respectively.
You can find the buttons section in mouse*.mou.
[translations]
This section contains scancode translations of the form:
number=number
Page 2 (printed 7/3/90)
xsconfig(X) X Version 11 (11 July 1990) xsconfig(X)
The number left of the equal sign is the original
scancode generated by pressing the key.
The number right of the equal sign is the new
(translated) scancode.
On 101-key personal computer keyboards, the dedicated
cursor keys produce a two-byte scancode. The first byte
is 0xE0. The second byte is the scancode of the
corresponding numeric keypad key. The translations
section is used to translate these two-byte scancodes to
a unique single-byte scancode.
You can find the translations sections in kb101.kbd.
[keyctrl]
This section allows any of several control flags to be
attached to particular keys. The keys are specified by
their scancodes as in the translations section. The
translations section has no effect on the scancodes
specified in the keyctrl section. Each line in the
keyctrl section has the form:
number: flag [flag . . .]
The following flags are used to specify locking keys.
Only one key should be associated with each of the
keyboard LEDs.
CapsLock: The CapsLock LED reflects the state of the
key.
NumLock: The NumLock LED reflects the state of the
key.
ScrollLock: The ScrollLock LED reflects the state of
the key.
PseudoLock: Locking is simulated, but no keyboard LED
is associated with the key. Any number of keys may
have this attribute.
The following additional attributes are allowed:
BiosIgnore: The codes generated by this key are hidden
from the BIOS. This attribute is useful for disabling
the actions of the print-screen and Pause keys. This
control flag is ignored on UNIX systems.
XIgnore: The codes generated by this key are not passed
to X clients. This attribute may be useful if you use
Page 3 (printed 7/3/90)
xsconfig(X) X Version 11 (11 July 1990) xsconfig(X)
the print-screen key to activate a screen-dump utility.
You can find the keyctrl section in KB*.KBD.
[modifiers]
This section defines the modifier keys, such as Shift,
Caps Lock, CTRL, and ALT, using the form:
number: modifiername
The number is the scancode, possibly translated, for the
key.
The modifiername is one of "Shift," "Lock," "Control," or
"Mod1" through "Mod5." Our convention is to use "Mod1"
for the ALT key.
You can find the modifiers section in kb*.kbd.
[keysyms]
The keysyms section provides the mapping between
scancodes and the glyphs associated with each key using
the form:
scancode: keysym [keysym . . .]
If the scancode has been translated in the translations
section, use the translated scancode.
Each keysym corresponds to a legend (glyph) on the key.
The translation currently used by most clients associates
the first keysym with the unshifted state and a second
keysym, if present, with the shifted state. For the
alphabetic keys, only the uppercase keysym is specified
and the value is converted to lowercase when unshifted.
Conventionally, the keysyms are the values defined in
keysyms.h.
Many non-U.S. keyboards have more than two symbols on
some keys. Conventionally, a key-often labeled AltGr-is
used to switch to this third symbol. It is possible to
use the modifiers section to attach a modifier bit (Mod1
though Mod5) to the AltGr key and assign more than two
keysyms to the affected keys in the keysyms section. It
is the responsibility of the clients to properly
interpret the association of the modifier bit with the
new keysyms.
You can find the keysyms section in kb*.kbd.
Page 4 (printed 7/3/90)
xsconfig(X) X Version 11 (11 July 1990) xsconfig(X)
FILES
/usr/lib/X11/xsconfig/config.txt
/usr/lib/X11/xsconfig/mouse*.mou
/usr/lib/X11/xsconfig/kb*.kbd
/usr/lib/X11/xsconfig/keysyms.h
/usr/lib/X11/.Xsight.cfg
SEE ALSO
X(X)
xinit(X)
COPYRIGHT
Copyright 1989, 1990, Locus Computing Corporation.
Page 5 (printed 7/3/90)