Chapter 1
Manual Pages
- NAME
- X - a portable, network-transparent window system
SYNOPSIS
The X Window System is a network transparent window system which runs on a wide range
of computing and graphics machines. It should be relatively straightforward to build the X
Consortium software distribution on most ANSI C and POSIX compliant systems. Commercial
implementations are also available for a wide range of platforms.
The X Consortium requests that the following names be used when referring to this
software:
X
X Window System
X Version 11
X Window System, Version 11
Xll
- X Window System is a trademark of X Consortium, Inc.
DESCRIPTION
X Window System servers run on computers with bitmap displays. The server distributes
user input to and accepts output requests from various client programs through a variety
of different interprocess communication channels. Although the most common case is for the
client programs to be running on the same machine as the server, clients can be run
transparently from other machines (including machines with different architectures and
operating systems) as well.
X supports overlapping hierarchical subwindows and text and graphics operations, on
both monochrome and color displays. For a full explanation of the functions that are
available, see the Xlib - C Language X Interface
manual, the X Window System Protocol printed specification, the X Toolkit Intrinsics - C Language Interface manual, and various toolkit documents.
The number of programs that use X is quite large. Programs provided in the core X
Consortium distribution include: a terminal emulator (xterm), a window manager (twm),
a display manager (xdm), a console redirect program (xconsole), a mail
interface (xmh), a bitmap editor (bitmap), resource listing/manipulation
tools (appres, editres), access control programs (xauth, xhost, and iceauth),
user preference setting programs (xrdb, xcmsdb, xset, xsetroot,
xstdcmap, and xmodmap), clocks (xclock and oclock), a font
displayer (xfd), utilities for listing information about fonts, windows, and
displays (xlsfonts, xwininfo, xlsclients, xdpyinfo, xlsatoms,
and xprop), screen image manipulation utilities (xwd, xwud, and xmag),
a performance measurement utility (xllperf), a font compiler (bdftopcf), a
font server and related utilities (xfs, fsinfo, fslsfonts, fstobdf),
a display server and related utilities (Xserver, rgb, mkfontdir), a
clipboard manager (xclipboard), a utility to terminate clients (xkill), and
a utility to cause part or all of the screen to be redrawn (xrefresh).
Many other utilities, window managers, games, toolkits, etc. are included as
user-contributed software in the X Consortium distribution, or are available using
anonymous ftp on the Internet. See your site administrator for details.
STARTING UP
There are two main ways of getting the X server and an initial set of client
applications started. The particular method used depends on what operating system you are
running and whether or not you use other window systems in addition to X.
xdm (the X Display Manager)
If you want to always have X running on your display, your site administrator can set
your machine up to use the X Display Manager xdm. This program is typically started
by the system at boot time and takes care of keeping the server running and getting users
logged in. If you are running xdm, you will see a window on the screen welcoming
you to the system and asking for your username and password. Simply type them in as you
would at a normal terminal, pressing the Return key after each. If you make a mistake, xdm
will display an error message and ask you to try again. After you have successfully logged
in, xdm will start up your X environment. By default, if you have an executable
file named .xsession in your home directory, xdm will treat it as a program
(or shell script) to run to start up your initial clients (such as terminal emulators,
clocks, a window manager, user settings for things like the background, the speed of the
pointer, etc.). Your site administrator can provide details.
xinit (run manually from the shell)
Sites that support more than one window system might choose to use the xinit program
for starting X manually. If this is true for your machine, your site administrator will
probably have provided a program named "xll", "startx", or
"xstart" that will do site-specific initialization (such as loading convenient
default resources, running a window manager, displaying a clock, and starting several
terminal emulators) in a nice way. If not, you can build such a script using the xinit program.
This utility simply runs one user-specified program to start the server, runs another to
start up any desired clients, and then waits for either to finish. Since either or both of
the user-specified programs may be a shell script, this gives substantial flexibility at
the expense of a nice interface. For this reason, xinit is not intended for end
users.
DISPLAY NAMES
From the user's prospective, every X server has a display name of the form:
hostname:displaynumber. screennumber
This information is used by the application to determine how it should connect to the
server and which screen it should use by default (on displays with multiple monitors):
hostname The hostname specifies the name of the machine to which the
display is physically connected. If the hostname is not given, the most efficient way of
communicating to a server on the same machine will be used.
displaynumber The phrase "display" is usually used to refer to
collection of monitors that share a common keyboard and pointer (mouse, tablet, etc.).
Most workstations tend to only have one keyboard, and therefore, only one display. Larger,
multi-user systems, however, frequently have several displays so that more than one person
can be doing graphics work at once. To avoid confusion, each display on a machine is
assigned a display number (beginning at 0) when the X server for that display is
started. The display number must always be given in a display name.
screennumber Some displays share a single keyboard and pointer among two or more
monitors. Since each monitor has its own set of windows, each screen is assigned a screen
number (beginning at 0) when the X server for that display is started. If the screen
number is not given, screen 0 will be used.
On POSIX systems, the default display name is stored in your DISPLAY environment
variable. This variable is set automatically by the xterm terminal emulator.
However, when you log into another machine on a network, you will need to set DISPLAY by
hand to point to your display. For example,
% setenv DISPLAY myws:0
$ DISPLAY= myws:0; export DISPLAY
The xon script can be used to start an X program on a remote machine; it
automatically sets the DISPLAY variable correctly.
Finally, most X programs accept a command line option of display displayname to
temporarily override the contents of DISPLAY. This is most commonly used to pop windows on
another person's screen or as part of a "remote shell" command to start an xterm
pointing back to your display. For example,
% xeyes -display joesws:0 -geometry 1000x1000+ 0+ 0
% rsh big xterm -display myws:0 -ls < /dev/null &
X servers listen for connections on a variety of different communications channels
(network byte streams, shared memory, etc.). Since there can be more than one way of
contacting a given server, The hostname part of the display name is used to
determine the type of channel (also called a transport layer) to be used. X servers
generally support the following types of connections:
local The hostname part of the display name should be the empty
string. For example: :0 :1, and :0.1. The most efficient local transport will be
chosen.
TCP/IP The hostname part of the display name should be the server
machine's IP address name. Full Internet names, abbreviated names, and IP addresses are
all allowed. For example: x.org:0, expo:0, 198.112.45.11:0, bigmachine:l, and hydra:0,1.
DECnet The hostname part of the display name should be the server machine's
nodename, followed by two colons instead of one. For example: myws::0, big::1, and hydra::0.1.
ACCESS CONTROL
An X server can use several types of access control. Mechanisms provided in Release 6
are:
|
Host Access |
Simple host-based access control |
|
MIT-MAGIC-COOKIE-1 |
Shared plain-text "cookies". |
|
XDM-AUTHORIZATION-1 |
Secure DES based private-keys. |
|
SUN-DES-1 |
Based on Sun's secure rpc system. |
|
MIT-KERBEROS-5 |
Kerberos Version 5 user-to-user. |
Xdm initializes access control for the server and also places authorization
information in a file accessible to the user. Normally, the list of hosts from which
connections are always accepted should be empty, so that only clients with are explicitly
authorized can connect to the display. When you add entries to the host list (with xhost),
the server no longer performs any authorization on connections from those machines. Be
careful with this.
The file from which Xlib extracts authorization data can be specified with the
environment variable XAUTHORITY, and defaults to the file. Xauthority in the
home directory. Xdm uses $HOME/.Xauthority and will create it or merge in
authorization records if it already exists when a user logs in.
If you use several machines and share a common home directory across all of the
machines by means of a network file system, you never really have to worry about
authorization files, the system should work correctly by default. Otherwise, as the
authorization files are machine-independent, you can simply copy the files to share them.
To manage authorization files, use xauth. This program allows you to extract
records and insert them into other files. Using this, you can send authorization to remote
machines when you login, if the remote machine does not share a common home directory with
your local machine.
Note that authorization information transmitted "in the clear" through a
network file system or using ftp or rsp can be "stolen" by a
network eavesdropper, and as such may enable unauthorized access. In many environments,
this level of security is not a concern, but if it is, you need to know the exact
semantics of the particular authorization data to know if this is actually a problem.
For more information on access control, see the Xsecurity manual page.
GEOMETRY SPECIFICATIONS
One of the advantages of using window systems instead of hardwired terminals is that
applications don't have to be restricted to a particular size or location on the screen.
Although the layout of windows on a display is controlled by the window manager that the
user is running (described below), most X programs accept a command line argument of the
form geometry WlDTHxHElGHT+XOFF+YOFF (where WIDTH, HEIGHT,XOFF, and YOFF
are numbers) for specifying a preferred size and location for this application's main
window.
The WIDTH and HEIGHT parts of the geometry specification are usually
measured in either pixels or characters, depending on the application. The XOFF and
YOFF parts are measured in pixels and are used to specify the distance of the
window from the left or right and top and bottom edges of the screen, respectively. Both
types of offsets are measured from the indicated edge of the screen to the corresponding
edge of the window. The X offset may be specified in the following ways:
+XOFF
The left edge of the window is to be placed XOFF pixels in from the left edge of
the screen (i.e., the X coordinate of the window's origin will be XOFF). XOFF may
be negative, in which case the window's left edge will be off the screen.
-XOFF
The right edge of the window is to be placed XOFF pixels in from the right edge
of the screen. XOFF may be negative, in which case the window's right edge will be
off the screen.
The Y offset has similar meanings:
+YOFF The top edge of the window is to be YOFF pixels below the top edge
of the screen (i.e., the Y coordinate of the window's origin will be YOFF). YOFF may
be negative, in which case the window's top edge will be off the screen.
-YOFF The bottom edge of the window is to be YOFF pixels above the bottom
edge of the screen.YOFF may be negative, in which case the window's bottom edge
will be off the screen.
Offsets must be given as pairs; in other words, in order to specify either XOFF or
YOFF both must be present. Windows can be placed in the four corners of the screen
using the following specifications:
+ 0 + 0 upper left hand corner.
- 0 + 0 upper right hand corner.
- 0 - 0 lower right hand corner.
+ 0 - 0 lower left hand corner.
In the following examples, a terminal emulator is placed in roughly the center of the
screen and a load average monitor, mailbox, and clock are placed in the upper right hand
corner:
xterm -fn 6
10 -geometry 8024+ 30+ 200 &
xclock -geometry 4848-0+ 0 &
xload -geometry 4848-96+ 0 &
xbiff -geometry 4848-48+ 0 &
WINDOW MANAGERS
The layout of windows on the screen is controlled by special programs called window
managers. Although many window managers will honor geometry specifications as given,
others may choose to ignore them (requiring the user to explicitly draw the window's
region on the screen with the pointer, for example).
Since window managers are regular (albeit complex) client programs, a variety of
different user interfaces can be built. The X Consortium distribution comes with a window
manager named twm which supports overlapping windows, popup menus, point-and-click
or click-to-type input models, title bars, nice icons (and an icon manager for those who
don't like separate icon windows).
See the user-contributed software in the X Consortium distribution for other popular
window managers.
FONT NAMES
Collections of characters for displaying text and symbols in X are known as fonts. A
font typically contains images that share a common appearance and look nice together (for
example, a single size, boldness, slant, and character set). Similarly, collections of
fonts that are based on a common type face (the variations are usually called roman, bold,
italic, bold italic, oblique, and bold oblique) are called families.
Fonts come in various sizes. The X server supports scalable fonts, meaning it is
possible to create a font of arbitrary size from a single source for the font. The server
supports scaling from outline fonts and bitmap fonts. Scaling from outline
fonts usually produces significantly better results than scaling from bitmap fonts.
An X server can obtain fonts from individual files stored in directories in the file
system, or from one or more font servers, or from a mixtures of directories and font
servers. The list of places the server looks when trying to find a font is controlled by
its font path. Although most installations will choose to have the server start up
with all of the commonly used font directories in the font path, the font path can be
changed at any time with the xset program. However, it is important to remember
that the directory names are on the server's machine, not on the application's.
Bitmap font files are usually created by compiling a textual font description into
binary form, using bdftopcf. Font databases are created by running the mkfontdir
program in the directory containing the source or compiled versions of the fonts.
Whenever fonts are added to a directory, mkfontdir should be rerun so that the
server can find the new fonts. To make the server reread the font database, reset the font
path with the xset program. For example, to add a font to a private directory, the
following commands could be used:
% cp newfont.pcf ~/myfonts
% mkfontdir~/myfonts
% xset fp rehash
The xfontsel and xisfonts programs can be used to browse through the
fonts available on a server. Font names tend to be fairly long as they contain all of the
information needed to uniquely identify individual fonts. However, the X server supports
wildcarding of font names, so the full specification
-adobe-courier-medium -r-normal--l 0-1 00-75-75-m-60-iso8859-1
might be abbreviated as:
-* -courier-medium -r-normal--* -100-* -* -* -* -iso8859-1
Because the shell also has special meanings for * and ?, wildcarded font names should
be quoted:
% xlsfonts -fn '-*-courier-medium-r-normal--*-100-*-*-*-*-*-*'
The xisfonts program can be used to list all of the fonts that match a given
pattern. With no arguments, it lists all available fonts. This will usually list the same
font at many different sizes. To see just the base scalable font names, try using one of
the following patterns:
-*-*-*-*-*-*-0-0-0-0-*-0-*-*
-*-*-*-*-*-*-0-0-75-75-*-0-*-*
-*-*-*-*-*-*-0-0-100-100-*-0-*-*
To convert one of the resulting names into a font at a specific size, replace one of
the first two zeros with a nonzero value. The field containing the first zero is for the
pixel size; replace it with a specific height in pixels to name a font at that size.
Alternatively, the field containing the second zero is for the point size; replace it with
a specific size in decipoints (there are 722.7 decipoints to the inch) to name a font at
that size. The last zero is an average width field, measured in tenths of pixels; some
servers will anamorphically scale if this value is specified.
FONT SERVER NAMES
One of the following forms can be used to name a font server that accepts TCP
connections:
tcp/hosleame:port
tcp/hostname:port/cataloguelist
The hostname specifies the name (or decimal numeric address) of the machine on
which the font server is running. The port is the decimal TCP port on which the
font server is listening for connections. The cataloguelist specifies a list of
catalogue names, with '+ ' as a separator.
Examples: tcpix.org:7100, tcpil 98. 112.4S.11 :71001all.
One of the following forms can be used to name a font server that accepts DECnet
connections:
decnet/nodename::font$objname
decnet/nodename::font$
The nodename specifies the name (or decimal numeric address) of the machine on
which the font server is running. The objnameis a normal, case-insensitive DECnet
object name. The cataloguelist specifies a list of catalogue names, with '+ ' as a
scparator.
Examples: DECnetlSRVNOD::FONT$DEFAULT, decnet/44.70::font$special/symbols.
COLOR NAMES
Most applications provide ways of tailoring (usually through resources or command line
arguments) the colors of various elements in the text and graphics they display. A color
can be specified either by an abstract color name, or by a numerical color specification.
The numerical specification can identify a color in either device-dependent (RGB) or
device-independent terms. Color strings are caseinsensitive .
X supports the use of abstract color names, for example, "red",
"blue". A value for this abstract name is obtained by searching one or more
color name databases. Xlib first searches zero or more client-side databases; the
number, location, and content of these databases is implementation dependent. If the name
is not found, the color is looked up in the X server's database. The text form of this
database is commonly stored in the file /usr/lib/X11/rgb.txt.
A numerical color specification consists of a color space name and a set of values in
the following syntax:
< color_space_name> :< value> /.../< value>
An RGB Device specification is identified by the prefix "rgb:" and has the
following syntax:
rgb:< red > /< green> /< blue>
< red>, < green>, < blue> := h | hh |
hhh | hhhh
h := single hexadecimal digits
Note that h indicates the value scaled in 4 bits, hh the value scaled in
8 bits, hhh the value scaled in 12 bits, and hhhh the value scaled in 16
bits, respectively. These values are passed directly to the X server, and are assumed to
be gamma corrected.
The eight primary colors can be represented as:
| black |
rgb:0/0/0 |
| red |
rgb:ffff/0/0 |
| green |
rgb:0/ffff/0 |
| blue |
rgb:0/0/ffff |
| yellow |
rgb:ffff/ffff/0 |
| magenta |
rgb:ffff/0/ffff |
| cyan |
rgb:0/ffff/ffff |
| white |
rgb:ffff/ffff/ffff |
For backward compatibility, an older syntax for RGB Device is supported, but its
continued use is not encouraged. The syntax is an initial sharp sign character followed by
a numeric specification, in one of the following formats:
| #RGB |
(4 bits each) |
| #RRGGBB |
(8 bits each) |
| #RRRGGGBBB |
(12 bits each) |
| #RRRRGGGGBBBB |
(16 bits each) |
The R, G, and B represent single hexadecimal digits. When fewer than 16 bits each are
specified, they represent the most-significant bits of the value (unlike the
"rgb:" syntax, in which values are scaled). For example, # 3a7 is the same as #
3000a0007000.
An RGB intensity specification is identified by the prefix "rgbi:" and has
the following syntax:
rgbi:< red> /< green> /< blue>
The red, green, and blue are floating point values between 0.0 and 1.0, inclusive. They
represent linear intensity values, with 1.0 indicating full intensity, 0.5 half intensity,
and so on. These values will be gamma corrected by Xlib before being sent to the X
server. The input format for these values is an optional sign, a string of numbers
possibly containing a decimal point, and an optional exponent field containing an E r e
followed by a possibly signed integer string.
- The standard device-independent string specifications have the following syntax:
-
| CIEXYZ:< X > / < Y > / < Z > |
(none, 1, none) |
| CIEuvY:< u > / < v > / < Y > |
(~.6, ~.6, 1) |
| CIExyY:< x > / < y > / < Y > |
(~.75, ~.85, 1) |
| CIELab:< L > / < a > / < b > |
(100, none, none) |
| CIELuv:< L > / < u > / < v > |
(100, none, none) |
| TekHVC:< H > / < V > / < C > |
(360, 100, 100) |
All of the values (C, H, V, X, Y, Z, a, b, u, v, y, x) are floating point values. Some
of the values are constrained to be between zero and some upper bound; the upper bounds
are given in parentheses above. The syntax for these values is an optional '+ ' or '-'
sign, a string of digits possibly containing a decimal point, and an optional exponent
field consisting of an 'E' or 'e' followed by an optional '+ ' or '-' followed by a string
of digits.
- For more information on device independent color, see the Xlib reference manual.
KEYBOARDS
The X keyboard model is broken into two layers: server-specific codes (called keycodes)
which represent the physical keys, and server-independent symbols (called keysyms)
which represent the letters or words that appear on the keys. Two tables are kept in the
server for converting keycodes to keysyms:
modifier list Some keys (such as Shift, Control, and Caps Lock) are known as modifier
and are used to select different symbols that are attached to a single key (such as
Shift-a generates a capital A, and Control-1 generates a control character ^L). The server
keeps a list of keycodes corresponding to the various modifier keys. Whenever a key is
pressed or released, the server generates an event that contains the keycode of the
indicated key as well as a mask that specifies which of the modifier keys are currently
pressed. Most servers set up this list to initially contain the various shift, control,
and shift lock keys on the keyboard.
keymap table
Applications translate event keycodes and modifier masks into keysyms using a keysym
table which contains one row for each keycode and one column for various modifier
states. This table is initialized by the server to correspond to normal typewriter
conventions. The exact semantics of how the table is interpreted to produce keysyms
depends on the particular program, libraries, and language input method used, but the
following conventions for the first four keysyms in each row are generally adhered to:
The first four elements of the list are split into two groups of keysyms. Group 1
contains the first and second keysyms; Group 2 contains the third and fourth keysyms.
Within each group, if the first element is alphabetic and the second element is the
special keysym NoSymbol, then the group is treated as equivalent to a group in
which the first element is the lowercase letter and the second element is the uppercase
letter.
Switching between groups is controlled by the keysym named MODE SWITCH, by attaching
that keysym to some key and attaching that key to any one of the modifiers Modl through
Mod5. This modifier is called the "group modifier." Group 1 is used when the
group modifier is off, and Group 2 is used when the group modifier is on.
Within a group, the modifier state determines which keysym to use. The first keysym is
used when the Shift and Lock modifiers are off. The second keysym is used when the Shift
modifier is on, when the Lock modifier is on and the second keysym is uppercase
alphabetic, or when the Lock modifier is on and is interpreted as ShiftLock. Otherwise,
when the Lock modifier is on and is interpreted as CapsLock, the state of the Shift
modifier is applied first to select a keysym; but if that keysym is lowercase alphabetic,
then the corresponding uppercase keysym is used instead.
OPTIONS
Most X programs attempt to use the same names for command line options and arguments.
All applications written with the X Toolkit Intrinsics automatically accept the following
options:
- display display This option specifies the name of the X server to use.
- geometry geometry This option specifies the initial size and location of the
window.
- bg color, -background color Either option specifies the color to use
for the window background.
- bd color, - bordercolor color Either option specifies the color to use
for the window border.
- bw number, - borderwidth number Either option specifies the width in
pixels of the window border.
- fg color, - foreground color Either option specifies the color to use
for text or graphics.
- fn font, -font font Either option specifies the font to use for
displaying text.
- iconic This option indicates that the user would prefer that the application's
windows initially not be visible as if the windows had be immediately iconified by the
user. Window managers may choose not to honor the application's request.
- name This option specifies the name under which resources for the application should
be found. This option is useful in shell aliases to distinguish between invocations of an
application, without resorting to creating links to alter the executable file name.
- rv, - reverse Either option indicates that the program should simulate reverse video
if possible, often by swapping the foreground and background colors. Not all programs
honor this or implement it correctly. It is usually only used on monochrome displays.
+ rv This option indicates that the program should not simulate reverse video. This is
used to override any defaults since reverse video doesn't always work properly.
- selectionTimeout This option specifies the timeout in milliseconds within which two
communicating applications must respond to one another for a selection request.
- synchronous This option indicates that requests to the X server should be sent
synchronously, instead of asynchronously. Since Xlib normally buffers requests to
the server, errors do not necessarily get reported immediately after they occur. This
option turns off the buffering so that the application can be debugged. It should never be
used with a working program.
- title string This option specifies the title to be used for this window. This
information is sometimes used by a window manager to provide some sort of header
identifying the window.
- xnllanguage language[_territory][.codeset]
This option specifies the language, territory, and codeset for use in resolving
resource and other filenames.
- xrm resourcestring This option specifies a resource name and value to override
any defaults. It is also very useful for setting resources that don't have explicit
command line arguments.
RESOURCES
To make the tailoring of applications to personal preferences easier, X provides a
mechanism for storing default values for program resources (e.g. background color, window
title, etc.) Resources are specified as strings that are read in from various places when
an application is run. Program components are named in a hierarchical fashion, with each
node in the hierarchy identified by a class and an instance name. At the top level is the
class and instance name of the application itself. By convention, the class name of the
application is the same as the program name, but with the first letter capitalized (e.g. Bitmap
or Emacs) although some programs that begin with the letter "x" also
capitalize the second letter for historical reasons.
The precise syntax for resources is:
|
ResourceLine |
= Comment | IncludeFile | ResourceSpec | <empty line> |
|
Comment |
= "!" {<any character except null or newline> } |
|
IncludeFile |
= "# " WhiteSpace "include" WhiteSpace FileName WhiteSpace |
|
FileName |
= <valid filename for operating system> |
|
ResourceSpec |
= WhiteSpace ResourceName WhiteSpacc ":" WhiteSpace Value |
|
ResourceName |
= [Binding] {Component Binding} ComponentName |
|
Binding |
= "." | "*" |
|
WhiteSpace |
= {< space> | <horizontal tab> } |
|
Component |
= "? " | ComponentName |
|
ComponentName |
= NameChar {NameChar} |
|
NameChar |
= "a"- "z" | "A"- "Z" l "0"-
"9" | "_" | "-" |
|
Value |
= { < any character except null or unescaped newline> } |
Elements separated by vertical bar (|) are alternatives. Curly braces ({...}) indicate
zero or more repetitions of the enclosed elements. Square brackets ([...]) indicate that
the enclosed element is optional. Quotes ("...") are used around literal
characters.
IncludeFile lines are interpreted by replacing the line with the contents of the
specified file. The word "include" must be in lowercase. The filename is
interpreted relative to the directory of the file in which the line occurs (for example,
if the filename contains no directory or contains a relative directory specification) .
If a ResourceName contains a contiguous sequence of two or more Binding characters, the
sequence will be replaced with single "." character if the sequence contains
only "." characters, otherwise the sequence will be replaced with a single
"*" character.
A resource database never contains more than one entry for a given ResourceName. If a
resource file contains multiple lines with the same ResourceName, the last line in the
file is used.
Any whitespace character before or after the name or colon in a ResourceSpec are
ignored. To allow a Value to begin with whitespace, the two-character sequence "
space" (backslash followed by space) is
recognized and replaced by a space character, and the two-character sequence "tab" (backslash followed by horizontal
tab) is recognized and replaced by a horizontal tab character. To allow a Value to contain
embedded newline characters, the two-character sequence "n" is recognized and replaced by a newline character. To allow
a Value to be broken across multiple lines in a text file, the two-character sequence
"newline" (backslash followed
by newline) is recognized and removed from the value. To allow a Value to contain
arbitrary character codes, the four-character sequence "4nnn", where each n is a digit character in the range of
"0"- "7", is recognized and replaced with a single byte that contains
the octal value specified by the sequence. Finally, the two-character sequence "S" is recognized and replaced with a single
backslash.
When an application looks for the value of a resource, it specifies a complete path in
the hierarchy, with both class and instance names. However, resource values are usually
given with only partially specified names and classes, using pattern matching constructs.
An asterisk (*) is a loose binding and is used to represent any number of intervening
components, including none. A period (.) is a tight binding and is used to separate
immediately adjacent components. A question mark (?) is used to match any single component
name or class. A database entry cannot end in a loose binding; the final component (which
cannot be "?") must be specified. The lookup algorithm searches the resource
database for the entry that most closely matches (is most specific for) the full name and
class being queried. When more than one database entry matches the full name and class,
precedence rules are used to select just one.
The full name and class are scanned from left to right (from highest level in the
hierarchy to lowest), one component at a time. At each level, the corresponding component
and/or binding of each matching entry is determined, and these matching components and
bindings are compared according to precedence rules. Each of the rules is applied at each
level, before moving to the next level, until a rule selects a single entry over all
others. The rules (in order of precedence) are:
- An entry that contains a matching component (whether name, class, or "?")
takes precedence over entries that elide the level (that is, entries that match the level
in a loose binding).
- An entry with a matching name takes precedence over both entries with a matching class
and entries that match using "?". An entry with a matching class takes
precedence over entries that match using "?".
- An entry preceded by a tight binding takes precedence over entries preceded by a loose
binding.
Programs based on the X Tookit Intrinsics obtain resources from the following sources
(other programs usually support some subset of these sources):
RESOURCE MANAGER root window property
Any global resources that should be available to clients on all machines should be
stored in the RESOURCE_MANAGER property on the root window of the first screen using the xrdb
program. This is frequently taken care of when the user starts up X through the
display manager or xinit.
SCREEN_RESOURCES root window property
Any resources specific to a given screen (e.g. colors) that should be available to
clients on all machines should be stored in the SCREEN_RESOURCES property on the root
window of that screen. The xrdb program will sort resources automatically and place
them in RESOURCE_MANAGER or SCREEN_RESOURCES, as appropriate.
application-specific files Directories named by the environment variable
XUSERFILESEARCHPATH or the environment variable XAPPLRESDIR (which names a single
directory and should end with a '/' on POSIX systems), plus directories in a standard
place (usually under /usr/lib/X11/, but this can be overridden with the XFILESEARCHPATH
environment variable) are searched for for application-specific resources. For example,
application default resources are usually kept in /usr/lib/X11/app-defaults/. See the X Toolkit Intrinsics - C Language Interface manual
for details.
XENVIRONMENT
Any user- and machine-specific resources may be specified by setting the XENVIRONMENT
environment variable to the name of a resource file to be loaded by all applications. If
this variable is not defined, a file named $HOME/.Xdefaults-hostname is
looked for instead, where hostname is the name of the host where the application is
executing.
- xrm resourcestring Resources can also be specified from the command line. The resourcestring
is a single resource name and value as shown above. Note that if the string contains
characters interpreted by the shell (e.g., asterisk), they must be quoted. Any number of -
xrm arguments may be given on the command line.
Program resources are organized into groups called classes, so that collections
of individual resources (each of which are called instances) can be set all at
once. By convention, the instance name of a resource begins with a lowercase letter and
class name with an upper case letter. Multiple word resources are concatenated with the
first letter of the succeeding words capitalized. Applications written with the X Toolkit
Intrinsics will have at least the following resources:
background (class Background) This resource specifies the color to use for the window
background.
borderWidth (class BorderWidth) This resource specifies the width in pixels of the
window border.
borderColor (class BorderColor) This resource specifies the color to use for the window
border.
Most applications using the X Toolkit Intrinsics also have the resource foreground
(class Foreground), specifying the color to use for text and graphics within the window.
By combining class and instance specifications, application preferences can be set
quickly and easily. Users of color displays will frequently want to set Background and
Foreground classes to particular defaults. Specific color instances such as text cursors
can then be overridden without having to define all of the related resources. For example,
bitmap*Dashed:off
XTerm*cursorColor: gold
XTerm*multiScroll: on
XTerm*jumpScroll: on
XTerm*reverseWrap: on
XTerm*curses: on
XTerm*Font: 610
XTerm*scrollBar: on
XTerm*scrollbar*thickness: 5
XTerm*multiClickTime: 500
XTerm*charClass: 33:48,37:48,45-47:48,64:48
XTerm*cutNewline: off
XTerm*cutToBeginningOfLine: off
X Term*tite Inhib it: on
XTerm*ttyModes: intr ^c erase ^? kill ^u
XLoad*Background: gold
XLoad*Foreground: red
XLoad*highlight: black
XLoad*borderWidth: 0
emacs*Geometry: 8065-0-0
emacs*Background: rgb:5b/76/86
emacs*Foreground: white
emacs*Cursor: white
emacs*BorderColor: white
emacs*Font: 610
xmag*geometry: -0-0
xmag*borderColor: white
If these resources were stored in a file called .Xresources in your home
directory, they could be added to any existing resources in the server with the following
command:
% xrdb -merge $HOME/.Xresources
This is frequently how user-friendly startup scripts merge user-specific defaults into
any site-wide defaults. All sites are encouraged to set up convenient ways of
automatically loading resources. See the Xlib Programming Manual section Resource Manager
Functions for more information.
EXAMPLES
DIAGNOSTICS
A wide variety of error messages are generated from various programs. The default error
handler in Xlib (also used by many toolkits) uses standard resources to construct
diagnostic messages when errors occur. The defaults for these messages are usually stored
in /usr/lib/X11/XErrorDB. If this file is not present, error messages will be
rather terse and cryptic.
When the X Toolkit Intrinsics encounter errors converting resource strings to the
appropriate internal format, no error messages are usually printed. This is convenient
when it is desirable to have one set of resources across a variety of displays (e.g. color
vs. monochrome, lots of fonts vs. very few, etc.), although it can pose problems for
trying to determine why an application might be failing. This behavior can be overridden
by the setting the StringConversionsWarning resource.
To force the X Toolkit Intrinsics to always print string conversion error messages, the
following resource should be placed in the file that gets loaded onto the RESOURCE_MANAGER
property using the xrdb program (frequently called .Xresources or .Xres in
the user's home directory):
*StringConversionWarnings: on
To have conversion messages printed for just a particular application, the appropriate
instance name can be placed before the asterisk:
xterm *StringConversionWarnings: on
SEE ALSO
XConsortiumf(1), XStandards(1), Xsecurity(1), appres(1), bdftopof(1),
bitmap(1), editres(1), fsinfo(1), fslsfonts(1), fstobdf(1), iceauth(1), mkfontdir(1),
oclock(1), rgb(1), resize(1), twm(1), xllperf(1), xllperfcomp(1), xauth(1), xclipboard(1),
xclock(1), xcmsdb(1), xconsole(1), xdm(1), xdpyinfo(1), xfd(1), xfs(1), xhost(1),
xinit(1), xkill(1), xlogof1), xlsatoms(1), xlsclients(1), xlsfonts(1), xmag(1), xmh(1),
xmodmap(1), xprop(1), xrdb(1), xrefresh(1), xset(1), xsetroot(1), xstdcmap(1), xterm(1),
xwd(1), xwininfo(1), xwud(1), Xserver(1), Xlib- C Language X
Interface, and X Toolkit Intrinsics - C
Language Interface
TRADEMARKS
X Window System is a trademark of X Consortium, Inc. Fresco is a registered trademark
of X Consortium, Inc.
AUTHORS
A cast of thousands, literally. The Release 6 distribution is brought to you by X
Consortium, Inc. The names of all people who made it a reality will be found in the
individual documents and source files. The staff members at the X Consortium responsible
for this release are: Donna Converse, Gary Cutbill, Stephen Gildea, Jay Hersh, Kaleb
Keithley, Matt Landau, Ralph Mor, Janet O'Halloran, Bob Scheifler, Ralph Swick, and Dave
Wiggins.
The X Window System standard was originally developed at the Laboratory for Computer
Science at the Massachusetts Institute of Technology, and all rights thereto were assigned
to the X Consortium on January 1, 1994.
- NAME
- X Standards- X Consortium Standards
- SYNOPSIS
-
The major goal of the X Consortium is to promote cooperation within the computer
industry in the creation of standard software interfaces at all layers in the X Window
System environment. The status of various standards, and the software in the X11R6
distribution, is explained below.
- STANDARDS
-
The following documents are X Consortium standards:
X Window System Protocol
X Version 11, Release 6
Robert W. Scheifler
Xlib - C Language X Interface
X Version 11, Release 6
James Gettys, Robert W. Scheifler, Ron Newman
X
Toolkit Intrinsics - C Language Interface
X Version 11, Release 6
Joel McCormack, Paul Asente, Ralph R. Swick, Donna Converse
Bitmap Distribution Format
Version 2.1
X Version 11, Release 6
Inter-Client Communication Conventions Manual
Version 2.0
X Version 11, Release 6
David Rosenthal, Stuart W. Marks
Compound Text Encoding
Version 1.1
X Version 11, Release 6
Robert W. Scheifler
X Logical Font Description Conventions
Version 1.5
X Version 11, Release 6 Jim Flowers, Stephen Gildea
X Display Manager Control Protocol
Version 1.0
X Version 11, Release 6
Keith Packard
X11 Nonrectangular Window Shape Extension
Version 1.0
X Version 11, Release 6
Keith Packard
X11 Input Extension Protocol Specification
Version 1.0
X Version 11, Release 6
George Sachs, Mark Patrick
X11 Input Extension Library Specification
X Version 11, Release 6
Mark Patrick, George Sachs
The X Font Service Protocol
Version 2.0
X Version 11, Release 6
Jim Fulton
PEX Protocol Specification
Version 5.1
Cheryl Huntington (architect), Paula Womack (editor)
PEXlib Specification and C Language Binding
Version 5.1
Jeff Stevenson
Inter-Client Exchange (ICE) Protocol
Version 1.0
X Version 11, Release 6
Robert Scheifler, Jordan Brown
lnter-Client Exchange (ICE) Library
Version 1.0
X Version 11, Release 6
Ralph Mor
X Session Management Protocol
Version 1.0
X Version 11, Release 6
Mike Wexler
X Session Management Library
Version 1.0
X Version 11, Release 6
Ralph Mor
The Input Method Protocol
Version 1.0
X Version 11, Release 6
Masahiko Narita, Hideki Hiura
X Synchronization Extension
Version 3.0
X Version 11, Release 6
Tim Glauert, Dave Carver, Jim Gettys, David P. Wiggins
X Image Extension, Protocol Reference Manual
Version 5.0
X Version 11, Release 6
Bob Shelley
XTEST Extension
Version 2.2
Kieron Drake
Big Requests Extension
Version 2.0
X Version 11, Release 6
Bob Scheifler
XC-MISC Extension
Version 1.1
X Version 11, Release 6
Bob Scheifler, Dave Wiggins
- DRAFT STANDARDS
-
The following documents are currently draft standards of the X Consortium.
X Image Extension Library
Public Review Draft
Gary Rogers
Extending X for Double-Buffering, Multi-Buffering, and Stereo
Version 3.3
Public Review Draft
Jeffrey Friedberg, Larry Seiler, Jeff Vroom
- INCLUDE FILES
-
The following include files are part of the Xlib standard.
< X11/cursorfont.h>
< X11/keysym.h>
< X11/keysymdef.h>
< X11/X.h>
< X11/Xatom.h>
< X11/Xcms.h>
< X11/Xlib.h>
< X11/Xlibint.h>
< X11/Xproto.h>
< X11/Xprotostr.h>
< X11/Xresource.h>
< X11/Xutil.h>
< X11/X10.h>
The following include files are part of the X Toolkit Intrinsics standard.
< X11/Composite.h>
< X11/CompositeP.h>
< X11/Constraint.h>
< X11/ConstrainP.h>
< X11/Core.h>
< X11/CoreP.h>
< X11/Intrinsic.h>
< X11/IntrinsicP.h>
< X11/Object.h>
< X11/ObjectP.h>
< X11/RectObj.h>
< X11/RectObjP.h>
< X11/Shell.h>
< X11/ShellP.h>
< X11/StringDefs.h>
< X11/Vendor.h>
< X11/VendorP.h>
The following include file is part of the Nonrectangular Window Shape Extension
standard.
< X11/extensions/shape.h>
The following include files are part of the X Input Extension standard.
< X11/extensions/XI.h>
< X11/extensions/XInput.h>
< X11/extensions/XIproto.h>
The following include files are part of the PEXlib standard.
< X11/PEX5/PEX.h>
< X11/PEX5/PEXlib.h>
< X11/PEX5/PEXlibint.h>
< X11/PEX5/PEXproto.h>
< X11/PEX5/PEXprotost.h>
The following include files are part of the ICElib standard.
< X 11/ICE/ICE .h>
< X 11/ICE/ICEconn.h>
< X11/ICE/ICElib.h>
< X11/ICE/ICEmsg.h>
< X11/ICE/ICEproto.h>
< X11/ICE/ICEutil.h>
The following include files are part of the SMlib standard.
< X11/SM/SM.h>
< X11/SM/SMlib.h>
< X11/SM/SMproto.h>
The following include file is part of the Synchronization standard.
< X11/extensions/sync.h>
The following include files are part of the XIElib draft standard.
< X11/extensions/XIE .h>
< X11/extensions/XIElib.h>
< X11/extensions/XIEproto.h>
< X11/extensions/XIEprotost.h>
The following include file is part of the XTEST standard.
< X11/extensions/XTest.h>
The following include file is part of the Multi-Buffering draft standard.
< X11/extensions/multibuf.h>
- NON STANDARDS
-
The X11R6 distribution contains sample implementations, not reference implementations.
Although much of the code is believed to be correct, the code should be assumed to be in
error wherever it conflicts with the specification.
The only X Consortium standards are the ones listed above. No other documents, include
files, or software in XllR6 carry special status within the X Consortium. For example,
none of the following are standards: internal interfaces of the sample server; the MIT-SHM
extension; the Athena Widget Set; the Xmu library; the Xau library; the RGB database; the
fonts distributed with XllR6; the applications distributed with XllR6; the include files
< X11/XWDFile.h>, < X11/Xfunsproto.h>, < X11/Xfuncs.h>, <
X11/Xosdefs.h>, < X11/Xos.h>, and < X11/Xthreads.h>; the bitmap files in
< X11/bitmaps>
The following are works in progress within the X Consortium, and are neither standards
nor draft standards: Fresco; Low Bandwidth X; X Keyboard Extension; Record Extension.
- NAME
-
X Consortium- X Consortium information
- SYNOPSIS
-
Release 6 of X Version 11 is brought to you by X Consortium, Inc.
- DESCRIPTION
-
The X Consortium is an independent, not-for-profit Delaware membership corporation. It
was formed in 1993 as the successor to the MIT X Consortium. The purpose of the X
Consortium is to foster the development, evolution, and maintenance of the X Window
System, a comprehensive set of vendor-neutral, system-architecture neutral,
network-transparent windowing and user interface standards.
The X Window System was created in the mid-1980s at the Massachusetts Institute of
Technology. In 1988, MIT formed a member-funded consortium to provide the technical and
administrative leadership necessary to support further development of the X Window System.
In 1992, MIT and the membership decided it was in their best interests to move the
consortium out of MIT and create an independent, stand-alone organization. All rights to
the X Window System were assigned by MIT to X Consortium, Inc. on January 1, 1994.
The X Consortium is financially self-supporting through membership fees. There are no
license fees associated with the use of X Window System standards and code developed by
the X Consortium. Membership in the X Consortium is open to any organization willing to
execute a membership agreement.
The X Consortium is a highly participative body. Members are encouraged to actively
cooperate with the staff and other members in the design and review of proposed
specifications, and in the design, coding and testing of sample implementations of those
specifications.
The X Consortium accomplishes most of its work using electronic mail over the Internet,
with individual mailing lists for working groups. Internet electronic mail connectivity
should be viewed as a requirement for useful participation in X Consortium activities.
Meetings are held as necessary, often in conjunction with industry conferences and trade
shows.
- STAFF
-
President: Bob Scheifler, rws@x.org, phone: (617) 374-1010
Office Manager: Janet O'Halloran, joh@x.org, phone: (617) 374-1011
Technical Director, Integration Technology: Ralph Swick, swick@x.org
Technical Director, Application Toolkits: Matt Landau, matt@ x.org
Technical Staff: Donna Converse, converse@x.org, Stephen Cildea, gildea@x.org, Jay Hersh,
hersh@x.org
Kaleb Keithley, kaleb@x.org, Ralph Mor, mor@x.org, Dave Wiggins, dpw@x.org
SysAdmin: Gary Cutbill, rgary@x.org
- BOARD OF DIRECTORS
- The X Consortium's activities and affairs are managed under the direction and oversight
of a Board of Directors, elected annually by the Members. The Board is responsible for
reviewing the achievements of the Consortium, approving planned work, appointing a
President and other officers of the Consortium, and setting membership dues. The current
Directors are:
Robert W. Scheifler, President, X Consortium
Dr. Porest Baskett, Senior VP of R&D, Silicon Graphics Computer Systems
Harold D. Blair, Partner, Partnerwerks
Roger S. Gourd, VP and Chief of Staff, Open Software Foundation
David Harris, Director, Adobe Systems [ex officio as Chairman, X Industry Association]
Dr. Robin Hillyard, Chairman and Chief Technical Officer, Novasoft Systems
Dr. Chong Lee, President and CEO, Phase X Systems, Inc.
Don McGovern, Vice President - UNIX Systems Group, Novell, Inc.
Therese E. Myers, President and CEO, Quarterdeck Office Systems
Peter 1. Shaw, President and CEO, AGE Logic, Inc.
Dan N. Turner, President and CEO, Petrotechnical Open Software Corporation
- ADDRESS
- The X Consortium can be reached at:
X Consortium
One Memorial Drive
Cambridge MA 02142-1301
Tel: (617) 374-1000
Fax: (617) 374-1025
membership@ x.org
You can reach the X Consortium on
the Wide World Web
or anonymous ftp to:
ftp.x.org
- FULL MEMBERS
- Adobe Systems Inc.
Apple Computer, Inc.
Cray Research, Inc.
Digital Equipment Corp.
Fujitsu Limited
Hewlett-Packard Company
Hitachi Ltd.
Hughes Aircraft Company
IBM Corporation
Kubota Corp.
Megatek Corp.
Motorola, Inc.
NCR Corporation (representing ADDS/NCR/AT&T)
NEC Corporation
Nippon Telegraph and Telephone Corporation
Oki Electric Industry Co., Ltd.
OMRON Corporation
The Santa Cruz Operation, Inc.
Siemens Nixdorf Informationssysteme AG
Silicon Graphics, Inc.
Sony Corporation
Sun Microsystems, Inc.
Tektronix, Inc.
Unix Systems Laboratories (includes Novell)
- ASSOCIATE MEMBERS CETIA - Compagnie Europeene des Techniques de l'Ingenierie Assistee
- Network Computing Devices
Quarterdeck Office Systems
Walker Richer & Quinn, Inc.
- AFFILIATE MEMBERS
- AGE Logic, Inc.
ASTEC, Inc.
ATR
BARCO Chromatics, Inc.
Congruent Corp.
Diagnostic/Retrieval Systems, Inc.
Gallium Software, Inc.
Georgia Institute of Technology
Human Designed Systems, Inc.
Hummingbird Communications Ltd.
Integrated Computer Solutions, Inc.
Investment Management Services, Inc.
IXI Limited
Japan Computer Corporation
Jupiter Systems
KAIST - Korean Advanced Institute of Science and Technology
Labtam Australia
Locus Computing Corporation
Mercury Interactive Corp.
Metheus Corporation
Metro Link, Inc.
M3i Systems, Inc.
Object Management Group, Inc.
Open Software Foundation O'Reilly & Associates, Inc.
ParcPlace Systems
Performance Awareness Corp.
Peritek Corp.
Petrotechnical Open Software Corp.
Phase X Systems, Inc.
SOUM Corporation
Tatung Science and Technology
Tech-Source, Inc.
User Interface Technologies Ltd.
Veritas Software, Inc.
VisiCom Laboratories, Inc.
VisionWare Ltd.
Visix Software, Inc.
Visual Information Technologies, Inc.
White Pine Software, Inc.
The XFree86 Project, Inc.
- NAME
- appres - list X application resource database
- SYNOPSIS
-
appres [[class [instance]] [- 1] [toolkitoptions]
- DESCRIPTION
-
The appres program prints the resources seen by an application (or subhierarchy
of an application) with the specified class and instance names. It can be
used to determine which resources a particular program will load. For example,
% appres Xterm
will list the resources that any xterm program will load. If no application
class is specified, the class -AppResTest- is used.
To match a particular instance name, specify an instance name explicitly after the
class name, or use the normal Xt toolkit option. For example, % appres XTerm myxterm
or
% appres XTerm - name myxterm
To list resources that match a subhierarchy of an application, specify hierarchical
class and instance names. The number of class and instance components must be equal, and
the instance name should not be specified with a toolkit option. For example,
% appres Xman.TopLevelShell.Form xman.topBox.form
will list the resources of widgets of xman topBox hierarchy. To list just the
resources matching a specific level in the hierarchy, use the - 1 option. For example,
% appres XTerm.VT100 xterm.vt100 - 1
will list the resources matching the xterm vt100 widget.
- SEE ALSO
- X(1), xrdb(1), listres(1)
- AUTHOR
- Jim Fulton, MIT X Consortium
- NAME
-
bdftopcf - convert X font from Bitmap Distribution Format to Portable Compiled Format
- SYNOPSIS
-
bdftopcf [ -pn ] [ -un ] [ -m ] [ -l ]
[ -M ] [ -L ] [ -t ] [ -i ] [ -o outputfile
]fontfile.bdf
- DESCRIPTION
-
Bdftopcf is a font compiler for the X server and font server. Fonts in Portable
Compiled Format can be read by any architecture, although the file is structured to allow
one particular architecture to read them directly without reformatting. This allows fast
reading on the appropriate machine, but the files are still portable (but read more
slowly) on other machines.
- OPTIONS
-
|
- pn |
Sets the font glyph padding. Each glyph in the font will have each scanline
padded in to a multiple of n bytes, where n is 1, 2, 4 or 8. |
|
- un |
Sets the font scanline unit. When the font bit order is different from the font byte
order, the scanline unit n describes what unit of data (in bytes) are to be
swapped; the unit i can be 1, 2 or 4 bytes. |
|
- m |
Sets the font bit order to MSB (most significant bit) first. Bits for each glyph will
be placed in this order; i.e., the left most bit on the screen will be in the highest
valued bit in each unit. |
|
- I |
Sets the font bit order to LSB (least significant bit) first. The left most bit on the
screen will be in the lowest valued bit in each unit. |
|
- M |
Sets the font byte order to MSB first. All multi-byte data in the file (metrics,
bitmaps and everything else) will be written most significant byte first. |
|
- L |
Sets the font byte order to LSB first. All multi-byte data in the file (metrics,
bitmaps and everything else) will be written least significant byte first. |
|
- t |
When this option is specified, bdftopcf will convert fonts into
"terminal" fonts when possible. A terminal font has each glyph image padded to
the same size; the X server can usually render these types of fonts more quickly. |
|
- i |
This option inhibits the normal computation of ink metrics. When a font has glyph
images which do not fill the bitmap image (i.e., the "on" pixels don't extend to
the edges of the metrics) bdftopof computes the actual ink metrics and places them
in the .pcf file; the - t option inhibits this behavior. |
|
- o output-file-name |
By default bdftopcf writes the pcf file to standard output; this option gives
the name of a file to be used instead. |
- SEE ALSO
- X(1)
- AUTHOR
- Keith Packard, MIT X Consortium
- NAME
-
bdftosnf - BDF to SNF font compiler for X11 Compiled Format
- SYNOPSIS
-
bdftosnf [-p# ][-u# ][-m][-l][-M][-L][-w][-W][-t][bdf-file]
- DESCRIPTION
- bdftosnf reads a Bitmap Distribution Format (BDF) font from the specified file
(or form standard input if no file is specified) and writes an Xll server normal font
(SNF) to standard output.
- OPTIONS
-
|
- p# |
Force the glyph padding to a specific number. The legal values are 1, 2, 4, and 8. |
|
- u# |
Force the scanline unit padding to a specific number. The legal values are 1, 2, and
4. |
|
- m |
Force the bit order to most significant bit first. |
|
- l |
Force the bit order to least significant bit first. |
|
- M |
Force the byte order to most significant bit first. |
|
- L |
Force the byte order to least significant bit first. |
|
- w |
Print warnings if the character bitmaps have bits set to one outside of their defined
width. |
|
- W |
Print warnings for characters with an encoding of -1; the default is to silently
ignore such characters. |
|
- t |
Expand glyphs in "terminal-emulator" fonts to fill the bounding box. |
- SEE ALSO
- X(1), Xserver(1)
"Bitmap Distribution Format 2.1"