1637 lines
58 KiB
HTML
1637 lines
58 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of X</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>X</H1>
|
|
Section: Environments, Tables, and Troff Macros (7)<BR>Updated: xorg-docs 1.7.1<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
X - a portable, network-transparent window system
|
|
<A NAME="lbAC"> </A>
|
|
<H2>OVERVIEW</H2>
|
|
|
|
<P>
|
|
|
|
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.Org Foundation software
|
|
distribution on most ANSI C and POSIX compliant systems. Commercial
|
|
implementations are also available for a wide range of platforms.
|
|
<P>
|
|
|
|
The X.Org Foundation requests that the following names be used when
|
|
referring to this software:
|
|
<P>
|
|
<CENTER><TABLE>
|
|
<TR VALIGN=top><TD ALIGN=center>X<BR></TD></TR>
|
|
<TR VALIGN=top><TD ALIGN=center>X Window System<BR></TD></TR>
|
|
<TR VALIGN=top><TD ALIGN=center>X Version 11<BR></TD></TR>
|
|
<TR VALIGN=top><TD ALIGN=center>X Window System, Version 11<BR></TD></TR>
|
|
<TR VALIGN=top><TD ALIGN=center>X11<BR></TD></TR>
|
|
</TABLE></CENTER>
|
|
|
|
<P>
|
|
<I>X Window System</I>
|
|
|
|
is a trademark of The Open Group.
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
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.
|
|
<P>
|
|
|
|
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 <I>Xlib - C Language X Interface</I> manual,
|
|
the <I>X Window System Protocol</I> specification,
|
|
the <I>X Toolkit Intrinsics - C Language Interface</I> manual,
|
|
and various toolkit documents.
|
|
<P>
|
|
|
|
The number of programs that use <I>X</I> is quite large.
|
|
Programs provided in the core X.Org Foundation distribution include:
|
|
a terminal emulator, <I>xterm</I>;
|
|
a window manager, <I>twm</I>;
|
|
a display manager, <I>xdm</I>;
|
|
a console redirect program, <I>xconsole</I>;
|
|
a mail interface, <I>xmh</I>;
|
|
a bitmap editor, <I>bitmap</I>;
|
|
resource listing/manipulation tools, <I>appres</I>, <I>editres</I>;
|
|
access control programs, <I>xauth</I>, <I>xhost</I>, and <I>iceauth</I>;
|
|
user preference setting programs, <I>xrdb</I>, <I>xcmsdb</I>,
|
|
<I>xset</I>, <I>xsetroot</I>, <I>xstdcmap</I>, and <I>xmodmap</I>;
|
|
clocks, <I>xclock</I> and <I>oclock</I>;
|
|
a font displayer, <I>xfd</I>;
|
|
utilities for listing information about fonts, windows, and displays,
|
|
<I>xlsfonts</I>, <I>xwininfo</I>, <I>xlsclients</I>,
|
|
<I>xdpyinfo</I>, <I>xlsatoms</I>, and <I>xprop</I>;
|
|
screen image manipulation utilities, <I>xwd</I>, <I>xwud</I>, and <I>xmag</I>;
|
|
a performance measurement utility, <I>x11perf</I>;
|
|
a font compiler, <I>bdftopcf</I>;
|
|
a font server and related utilities, <I>xfs</I>, <I>fsinfo</I>, <I>fslsfonts</I>, <I>fstobdf</I>;
|
|
a display server and related utilities, <I>Xserver</I>, <I>rgb</I>, <I>mkfontdir</I>;
|
|
a clipboard manager, <I>xclipboard</I>;
|
|
keyboard description compiler and related utilities, <I>xkbcomp</I>, <I>setxkbmap</I>
|
|
<I>xkbprint</I>, <I>xkbbell</I>, <I>xkbevd</I>, <I>xkbvleds</I>, and <I>xkbwatch</I>;
|
|
a utility to terminate clients, <I>xkill</I>;
|
|
a firewall security proxy, <I>xfwp</I>;
|
|
a proxy manager to control them, <I>proxymngr</I>;
|
|
a utility to find proxies, <I>xfindproxy</I>;
|
|
web browser plug-ins, <I>libxrx.so</I> and <I>libxrxnest.so</I>;
|
|
an RX MIME-type helper program, <I>xrx</I>;
|
|
and a utility to cause part or all of the screen to be redrawn, <I>xrefresh</I>.
|
|
<P>
|
|
|
|
Many other utilities, window managers, games, toolkits, etc. are included
|
|
as user-contributed software in the X.Org Foundation distribution, or are
|
|
available on the Internet.
|
|
See your site administrator for details.
|
|
<A NAME="lbAE"> </A>
|
|
<H2>STARTING UP</H2>
|
|
|
|
<P>
|
|
|
|
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.
|
|
<DL COMPACT>
|
|
<DT id="1"><B>Display Manager</B>
|
|
|
|
<DD>
|
|
If you want to always have X running on your display, your site administrator
|
|
can set your machine up to use a Display Manager such as <I>xdm</I>, <I>gdm</I>,
|
|
or <I>kdm</I>. 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 one of these
|
|
display managers, you will normally see a window on the screen welcoming you
|
|
to the system and asking for your login information. Simply type them in as
|
|
you would at a normal terminal. If you make a mistake, the display manager
|
|
will display an error message and ask you to try again. After you
|
|
have successfully logged in, the display manager will start up your X
|
|
environment. The documentation for the display manager you use can provide
|
|
more details.
|
|
<DT id="2"><B></B><I>xinit</I> (run manually from the shell)
|
|
|
|
<DD>
|
|
Sites that support more than one window system might choose to use the
|
|
<I>xinit</I> program for starting X manually. If this is true for your
|
|
machine, your site administrator will probably have provided a program
|
|
named "x11", "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 <I>xinit</I> 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, <I>xinit</I> is not intended for end users.
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>DISPLAY NAMES</H2>
|
|
|
|
<P>
|
|
|
|
From the user's perspective, every X server has a <I>display name</I> of the
|
|
form:
|
|
<P>
|
|
<DL COMPACT><DT id="3"><DD>
|
|
<I>hostname:displaynumber.screennumber</I>
|
|
</DL>
|
|
|
|
<P>
|
|
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):
|
|
<DL COMPACT>
|
|
<DT id="4"><I>hostname</I>
|
|
|
|
<DD>
|
|
The <I>hostname</I> 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.
|
|
<DT id="5"><I>displaynumber</I>
|
|
|
|
<DD>
|
|
The phrase "display" is usually used to refer to a collection of monitors that
|
|
share a common set of input devices (keyboard, mouse, tablet, etc.).
|
|
Most workstations tend to only have 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 <I>display number</I> (beginning at 0)
|
|
when the X server for that display is started. The display number must always
|
|
be given in a display name.
|
|
<DT id="6"><I>screennumber</I>
|
|
|
|
<DD>
|
|
Some displays share their input devices among two or more monitors.
|
|
These may be configured as a single logical screen, which allows windows to
|
|
move across screens, or as individual screens, each with their own set of
|
|
windows. If configured such that each monitor has its own set of windows,
|
|
each screen is assigned a
|
|
<I>screen number</I> (beginning at 0) when the X server for that display is
|
|
started. If the screen number is not given, screen 0 will be used.
|
|
</DL>
|
|
<P>
|
|
|
|
On POSIX systems, the default display name is stored
|
|
in your DISPLAY environment variable. This variable is set automatically
|
|
by the <I>xterm</I> terminal emulator. However, when you log into another
|
|
machine on a network, you may need to set DISPLAY by hand to point to your
|
|
display. For example,
|
|
<P>
|
|
|
|
<PRE>
|
|
% setenv DISPLAY myws:0
|
|
$ DISPLAY=myws:0; export DISPLAY
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
The <I>ssh</I> program can be used to start an X program on a remote machine;
|
|
it automatically sets the DISPLAY variable correctly.
|
|
<P>
|
|
|
|
Finally, most X programs accept a command line option of
|
|
<B>-display </B><I>displayname</I> 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,
|
|
<P>
|
|
<PRE>
|
|
% xeyes -display joesws:0 -geometry 1000x1000+0+0
|
|
% rsh big xterm -display myws:0 -ls </dev/null &
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
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 <I>hostname</I> 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:
|
|
<DL COMPACT>
|
|
<DT id="7"><I>local</I>
|
|
|
|
<DD>
|
|
<BR>
|
|
|
|
The hostname part of the display name should be the empty string.
|
|
For example: <I>:0</I>, <I>:1</I>, and <I>:0.1</I>. The most efficient
|
|
local transport will be chosen.
|
|
<DT id="8"><I>TCP/IP</I>
|
|
|
|
<DD>
|
|
<BR>
|
|
|
|
The hostname part of the display name should be the server machine's
|
|
hostname or IP address. Full Internet names, abbreviated names, IPv4
|
|
addresses, and IPv6 addresses are all allowed. For example:
|
|
<I>x.org:0</I>, <I>expo:0</I>, <I>[::1]:0</I>,
|
|
<I>198.112.45.11:0</I>, <I>bigmachine:1</I>, and <I>hydra:0.1</I>.
|
|
</DL>
|
|
<P>
|
|
|
|
<A NAME="lbAG"> </A>
|
|
<H2>ACCESS CONTROL</H2>
|
|
|
|
An X server can use several types of access control. Mechanisms provided
|
|
in Release 7 are:
|
|
<TABLE>
|
|
<TR VALIGN=top><TD>Host Access </TD><TD>Simple host-based access control.<BR></TD></TR>
|
|
<TR VALIGN=top><TD>MIT-MAGIC-COOKIE-1</TD><TD>Shared plain-text "cookies".<BR></TD></TR>
|
|
<TR VALIGN=top><TD>XDM-AUTHORIZATION-1</TD><TD>Secure DES based private-keys.<BR></TD></TR>
|
|
<TR VALIGN=top><TD>SUN-DES-1 </TD><TD>Based on Sun's secure rpc system.<BR></TD></TR>
|
|
<TR VALIGN=top><TD>Server Interpreted</TD><TD>Server-dependent methods of access control<BR></TD></TR>
|
|
</TABLE>
|
|
|
|
<P>
|
|
|
|
<I>Xdm</I> initializes access control for the server and also places
|
|
authorization information in a file accessible to the user.
|
|
<P>
|
|
|
|
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 <I>xhost</I>), the server no longer performs any
|
|
authorization on connections from those machines. Be careful with this.
|
|
<P>
|
|
|
|
The file from which <I>Xlib</I> extracts authorization data can be
|
|
specified with the environment variable <B>XAUTHORITY</B>, and defaults to
|
|
the file <B>.Xauthority</B> in the home directory. <I>Xdm</I> uses
|
|
<B>$HOME/.Xauthority</B> and will create it or merge in authorization records
|
|
if it already exists when a user logs in.
|
|
<P>
|
|
|
|
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 <I>xauth</I>.
|
|
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 <I>ftp</I> or <I>rcp</I> 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.
|
|
<P>
|
|
|
|
For more information on access control, see the
|
|
<I><A HREF="/cgi-bin/man/man2html?7+Xsecurity">Xsecurity</A></I>(7) manual page.
|
|
<A NAME="lbAH"> </A>
|
|
<H2>GEOMETRY SPECIFICATIONS</H2>
|
|
|
|
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 <B>-geometry </B><I>WIDTHxHEIGHT+XOFF+YOFF</I>
|
|
(where <I>WIDTH</I>, <I>HEIGHT</I>, <I>XOFF</I>, and <I>YOFF</I> are numbers)
|
|
for specifying a preferred size and location for this application's main
|
|
window.
|
|
<P>
|
|
|
|
The <I>WIDTH</I> and <I>HEIGHT</I> parts of the geometry specification are
|
|
usually measured in either pixels or characters, depending on the application.
|
|
The <I>XOFF</I> and <I>YOFF</I> 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:
|
|
<DL COMPACT>
|
|
<DT id="9"><I>+XOFF</I>
|
|
|
|
<DD>
|
|
The left edge of the window is to be placed <I>XOFF</I> pixels in from the
|
|
left edge of the screen (i.e., the X coordinate of the window's origin will be
|
|
<I>XOFF</I>). <I>XOFF</I> may be negative, in which case the window's left edge
|
|
will be off the screen.
|
|
<DT id="10"><I>-XOFF</I>
|
|
|
|
<DD>
|
|
The right edge of the window is to be placed <I>XOFF</I> pixels in from the
|
|
right edge of the screen. <I>XOFF</I> may be negative, in which case the
|
|
window's right edge will be off the screen.
|
|
</DL>
|
|
<P>
|
|
|
|
The Y offset has similar meanings:
|
|
<DL COMPACT>
|
|
<DT id="11"><I>+YOFF</I>
|
|
|
|
<DD>
|
|
The top edge of the window is to be <I>YOFF</I> pixels below the
|
|
top edge of the screen (i.e., the Y coordinate of the window's origin will be
|
|
<I>YOFF</I>). <I>YOFF</I> may be negative, in which case the window's top edge
|
|
will be off the screen.
|
|
<DT id="12"><I>-YOFF</I>
|
|
|
|
<DD>
|
|
The bottom edge of the window is to be <I>YOFF</I> pixels above the
|
|
bottom edge of the screen. <I>YOFF</I> may be negative, in which case
|
|
the window's bottom edge will be off the screen.
|
|
</DL>
|
|
<P>
|
|
|
|
Offsets must be given as pairs; in other words, in order to specify either
|
|
<I>XOFF</I> or <I>YOFF</I> both must be present. Windows can be placed in the
|
|
four corners of the screen using the following specifications:
|
|
<DL COMPACT>
|
|
<DT id="13"><I>+0+0</I>
|
|
|
|
<DD>
|
|
upper left hand corner.
|
|
<DT id="14"><I>-0+0</I>
|
|
|
|
<DD>
|
|
upper right hand corner.
|
|
<DT id="15"><I>-0-0</I>
|
|
|
|
<DD>
|
|
lower right hand corner.
|
|
<DT id="16"><I>+0-0</I>
|
|
|
|
<DD>
|
|
lower left hand corner.
|
|
</DL>
|
|
<P>
|
|
|
|
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:
|
|
<P>
|
|
<PRE>
|
|
xterm -fn 6x10 -geometry 80x24+30+200 &
|
|
xclock -geometry 48x48-0+0 &
|
|
xload -geometry 48x48-96+0 &
|
|
xbiff -geometry 48x48-48+0 &
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
<A NAME="lbAI"> </A>
|
|
<H2>WINDOW MANAGERS</H2>
|
|
|
|
The layout of windows on the screen is controlled by special programs called
|
|
<I>window managers</I>. 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).
|
|
<P>
|
|
|
|
Since window managers are regular (albeit complex) client programs,
|
|
a variety of different user interfaces can be built. The X.Org Foundation distribution
|
|
comes with a window manager named <I>twm</I> 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).
|
|
<P>
|
|
|
|
See the user-contributed software in the X.Org Foundation distribution for other
|
|
popular window managers.
|
|
<A NAME="lbAJ"> </A>
|
|
<H2>FONT NAMES</H2>
|
|
|
|
Collections of characters for displaying text and symbols in X are known as
|
|
<I>fonts</I>. 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 <I>families</I>.
|
|
<P>
|
|
|
|
Fonts come in various sizes. The X server supports <I>scalable</I> fonts,
|
|
meaning it is possible to create a font of arbitrary size from a single
|
|
source for the font. The server supports scaling from <I>outline</I>
|
|
fonts and <I>bitmap</I> fonts. Scaling from outline fonts usually produces
|
|
significantly better results than scaling from bitmap fonts.
|
|
<P>
|
|
|
|
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 <I>font path</I>. 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 <I>xset</I> program.
|
|
However, it is important to remember that the directory names are
|
|
on the <B>server</B>'s machine, not on the application's.
|
|
<P>
|
|
|
|
Bitmap font files are usually created by compiling a textual font description
|
|
into binary form, using <I>bdftopcf</I>.
|
|
Font databases are created by running the <I>mkfontdir</I> program in the
|
|
directory containing the source or compiled versions of the fonts.
|
|
Whenever fonts are added to a directory, <I>mkfontdir</I> 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 <I>xset</I> program. For example,
|
|
to add a font to a private directory, the following commands could be used:
|
|
<P>
|
|
<PRE>
|
|
% cp newfont.pcf ~/myfonts
|
|
% mkfontdir ~/myfonts
|
|
% xset fp rehash
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
The <I>xfontsel</I> and <I>xlsfonts</I> 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
|
|
<P>
|
|
<PRE>
|
|
<I>-adobe-courier-medium-r-normal--10-100-75-75-m-60-iso8859-1</I>
|
|
</PRE>
|
|
|
|
<P>
|
|
might be abbreviated as:
|
|
<P>
|
|
<PRE>
|
|
<I>-*-courier-medium-r-normal--*-100-*-*-*-*-iso8859-1</I>
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
Because the shell also has special meanings for <I>*</I> and <I>?</I>,
|
|
wildcarded font names should be quoted:
|
|
<P>
|
|
<PRE>
|
|
% xlsfonts -fn '-*-courier-medium-r-normal--*-100-*-*-*-*-*-*'
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
The <I>xlsfonts</I> 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:
|
|
<P>
|
|
<PRE>
|
|
<I>-*-*-*-*-*-*-0-0-0-0-*-0-*-*</I>
|
|
<I>-*-*-*-*-*-*-0-0-75-75-*-0-*-*</I>
|
|
<I>-*-*-*-*-*-*-0-0-100-100-*-0-*-*</I>
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
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.
|
|
<A NAME="lbAK"> </A>
|
|
<H2>FONT SERVER NAMES</H2>
|
|
|
|
One of the following forms can be used to name a font server that
|
|
accepts TCP connections:
|
|
<P>
|
|
<PRE>
|
|
tcp/<I>hostname</I>:<I>port</I>
|
|
tcp/<I>hostname</I>:<I>port</I>/<I>cataloguelist</I>
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
The <I>hostname</I> specifies the name (or decimal numeric address)
|
|
of the machine on which the font server is running. The <I>port</I>
|
|
is the decimal TCP port on which the font server is listening for connections.
|
|
The <I>cataloguelist</I> specifies a list of catalogue names,
|
|
with '+' as a separator.
|
|
<P>
|
|
|
|
Examples: <I>tcp/x.org:7100</I>, <I>tcp/198.112.45.11:7100/all</I>.
|
|
<A NAME="lbAL"> </A>
|
|
<H2>COLOR NAMES</H2>
|
|
|
|
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 case-insensitive.
|
|
<P>
|
|
|
|
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.
|
|
<I>Xlib</I> 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
|
|
<I>/usr/share/X11/rgb.txt</I>.
|
|
<P>
|
|
|
|
A numerical color specification
|
|
consists of a color space name and a set of values in the following syntax:
|
|
<P>
|
|
<PRE>
|
|
<I><color_space_name></I>:<I><value>/.../<value></I>
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
An RGB Device specification is identified by
|
|
the prefix "rgb:" and has the following syntax:
|
|
<P>
|
|
<PRE>
|
|
rgb:<I><red>/<green>/<blue></I>
|
|
|
|
<I><red></I>, <I><green></I>, <I><blue></I> := <I>h</I> | <I>hh</I> | <I>hhh</I> | <I>hhhh</I>
|
|
<I>h</I> := single hexadecimal digits
|
|
</PRE>
|
|
|
|
<P>
|
|
Note that <I>h</I> indicates the value scaled in 4 bits,
|
|
<I>hh</I> the value scaled in 8 bits,
|
|
<I>hhh</I> the value scaled in 12 bits,
|
|
and <I>hhhh</I> the value scaled in 16 bits, respectively.
|
|
These values are passed directly to the X server,
|
|
and are assumed to be gamma corrected.
|
|
<P>
|
|
|
|
The eight primary colors can be represented as:
|
|
<P>
|
|
<CENTER><TABLE>
|
|
<TR VALIGN=top><TD>black</TD><TD>rgb:0/0/0<BR></TD></TR>
|
|
<TR VALIGN=top><TD>red</TD><TD>rgb:ffff/0/0<BR></TD></TR>
|
|
<TR VALIGN=top><TD>green</TD><TD>rgb:0/ffff/0<BR></TD></TR>
|
|
<TR VALIGN=top><TD>blue</TD><TD>rgb:0/0/ffff<BR></TD></TR>
|
|
<TR VALIGN=top><TD>yellow</TD><TD>rgb:ffff/ffff/0<BR></TD></TR>
|
|
<TR VALIGN=top><TD>magenta</TD><TD>rgb:ffff/0/ffff<BR></TD></TR>
|
|
<TR VALIGN=top><TD>cyan</TD><TD>rgb:0/ffff/ffff<BR></TD></TR>
|
|
<TR VALIGN=top><TD>white</TD><TD>rgb:ffff/ffff/ffff<BR></TD></TR>
|
|
</TABLE></CENTER>
|
|
|
|
<P>
|
|
|
|
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:
|
|
<P>
|
|
<CENTER><TABLE>
|
|
<TR VALIGN=top><TD>#RGB </TD><TD>(4 bits each)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>#RRGGBB </TD><TD>(8 bits each)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>#RRRGGGBBB</TD><TD>(12 bits each)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>#RRRRGGGGBBBB</TD><TD>(16 bits each)<BR></TD></TR>
|
|
</TABLE></CENTER>
|
|
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
An RGB intensity specification is identified
|
|
by the prefix "rgbi:" and has the following syntax:
|
|
<P>
|
|
<PRE>
|
|
rgbi:<I><red>/<green>/<blue></I>
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
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 <I>Xlib</I>
|
|
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 or e
|
|
followed by a possibly signed integer string.
|
|
<P>
|
|
|
|
The standard device-independent string specifications have
|
|
the following syntax:
|
|
<P>
|
|
<CENTER><TABLE>
|
|
<TR VALIGN=top><TD>CIEXYZ:<I><X>/<Y>/<Z></I></TD><TD>(<I>none</I>, 1, <I>none</I>)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>CIEuvY:<I><u>/<v>/<Y></I></TD><TD>(~.6, ~.6, 1)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>CIExyY:<I><x>/<y>/<Y></I></TD><TD>(~.75, ~.85, 1)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>CIELab:<I><L>/<a>/<b></I></TD><TD>(100, <I>none</I>, <I>none</I>)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>CIELuv:<I><L>/<u>/<v></I></TD><TD>(100, <I>none</I>, <I>none</I>)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>TekHVC:<I><H>/<V>/<C></I></TD><TD>(360, 100, 100)<BR></TD></TR>
|
|
</TABLE></CENTER>
|
|
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
For more information on device independent color,
|
|
see the <I>Xlib</I> reference manual.
|
|
<A NAME="lbAM"> </A>
|
|
<H2>KEYBOARDS</H2>
|
|
|
|
<P>
|
|
|
|
The X keyboard model is broken into two layers: server-specific codes
|
|
(called <I>keycodes</I>) which represent the physical keys, and
|
|
server-independent symbols (called <I>keysyms</I>) which
|
|
represent the letters or words that appear on the keys.
|
|
Two tables are kept in the server for converting keycodes to keysyms:
|
|
<DL COMPACT>
|
|
<DT id="17"><I>modifier list</I>
|
|
|
|
<DD>
|
|
Some keys (such as Shift, Control, and Caps Lock) are known as <I>modifier</I>
|
|
and are used to select different symbols that are attached to a single key
|
|
(such as Shift-a generates a capital A, and Control-l 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 <I>event</I> 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.
|
|
<DT id="18"><I>keymap table</I>
|
|
|
|
<DD>
|
|
Applications translate event keycodes and modifier masks into keysyms
|
|
using a <I>keysym table</I> 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:
|
|
</DL>
|
|
<P>
|
|
|
|
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
|
|
the second element is the special keysym <I>NoSymbol</I>,
|
|
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.
|
|
<P>
|
|
|
|
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 Mod1 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.
|
|
<P>
|
|
|
|
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.
|
|
<A NAME="lbAN"> </A>
|
|
<H2>OPTIONS</H2>
|
|
|
|
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:
|
|
<DL COMPACT>
|
|
<DT id="19"><B>-display </B><I>display</I>
|
|
|
|
<DD>
|
|
This option specifies the name of the X server to use.
|
|
<DT id="20"><B>-geometry </B><I>geometry</I>
|
|
|
|
<DD>
|
|
This option specifies the initial size and location of the window.
|
|
<DT id="21"><B>-bg </B><I>color</I>, <B>-background </B><I>color</I>
|
|
|
|
<DD>
|
|
Either option specifies the color to use for the window background.
|
|
<DT id="22"><B>-bd </B><I>color</I>, <B>-bordercolor </B><I>color</I>
|
|
|
|
<DD>
|
|
Either option specifies the color to use for the window border.
|
|
<DT id="23"><B>-bw </B><I>number</I>, <B>-borderwidth </B><I>number</I>
|
|
|
|
<DD>
|
|
Either option specifies the width in pixels of the window border.
|
|
<DT id="24"><B>-fg </B><I>color</I>, <B>-foreground </B><I>color</I>
|
|
|
|
<DD>
|
|
Either option specifies the color to use for text or graphics.
|
|
<DT id="25"><B>-fn </B><I>font</I>, <B>-font </B><I>font</I>
|
|
|
|
<DD>
|
|
Either option specifies the font to use for displaying text.
|
|
<DT id="26"><B>-iconic</B>
|
|
|
|
<DD>
|
|
<BR>
|
|
|
|
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.
|
|
<DT id="27"><B>-name</B>
|
|
|
|
<DD>
|
|
<BR>
|
|
|
|
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.
|
|
<DT id="28"><B>-rv</B>, <B>-reverse</B>
|
|
|
|
<DD>
|
|
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.
|
|
<DT id="29"><B>+rv</B>
|
|
|
|
<DD>
|
|
<BR>
|
|
|
|
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.
|
|
<DT id="30"><B>-selectionTimeout</B>
|
|
|
|
<DD>
|
|
This option specifies the timeout in milliseconds within which two
|
|
communicating applications must respond to one another for a selection
|
|
request.
|
|
<DT id="31"><B>-synchronous</B>
|
|
|
|
<DD>
|
|
This option indicates that requests to the X server should be sent
|
|
synchronously, instead of asynchronously. Since
|
|
<I>Xlib</I>
|
|
|
|
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.
|
|
<DT id="32"><B>-title </B><I>string</I>
|
|
|
|
<DD>
|
|
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.
|
|
<DT id="33"><B>-xnllanguage </B><I>language[_territory][.codeset]</I>
|
|
|
|
<DD>
|
|
This option specifies the language, territory, and codeset for use in
|
|
resolving resource and other filenames.
|
|
<DT id="34"><B>-xrm </B><I>resourcestring</I>
|
|
|
|
<DD>
|
|
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.
|
|
</DL>
|
|
<A NAME="lbAO"> </A>
|
|
<H2>RESOURCES</H2>
|
|
|
|
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.) that is used by programs that
|
|
use toolkits based on the X Toolkit Intrinsics library libXt. (Programs
|
|
using the common Gtk+ and Qt toolkits use other configuration mechanisms.)
|
|
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. <I>Bitmap</I> or <I>Emacs</I>)
|
|
although some programs that begin with the letter ``x'' also capitalize the
|
|
second letter for historical reasons.
|
|
<P>
|
|
|
|
The precise syntax for resources is:
|
|
<P>
|
|
|
|
<PRE>
|
|
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 WhiteSpace ":" WhiteSpace Value
|
|
ResourceName = [Binding] {Component Binding} ComponentName
|
|
Binding = "." | "*"
|
|
WhiteSpace = {<space> | <horizontal tab>}
|
|
Component = "?" | ComponentName
|
|
ComponentName = NameChar {NameChar}
|
|
NameChar = "a"-"z" | "A"-"Z" | "0"-"9" | "_" | "-"
|
|
Value = {<any character except null or unescaped newline>}
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
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).
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
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 ``\<I>space</I>'' (backslash followed by space)
|
|
is recognized and replaced by a space character,
|
|
and the two-character sequence ``\<I>tab</I>''
|
|
(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 ``\<I>newline</I>''
|
|
(backslash followed by newline) is
|
|
recognized and removed from the value.
|
|
To allow a Value to contain arbitrary character codes,
|
|
the four-character sequence ``\<I>nnn</I>'',
|
|
where each <I>n</I> 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 ``\\'' is recognized
|
|
and replaced with a single backslash.
|
|
<P>
|
|
|
|
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.
|
|
<P>
|
|
|
|
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:
|
|
<DL COMPACT>
|
|
<DT id="35">1.<DD>
|
|
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).
|
|
<DT id="36">2.<DD>
|
|
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 "?".
|
|
<DT id="37">3.<DD>
|
|
An entry preceded by a tight binding takes precedence over entries
|
|
preceded by a loose binding.
|
|
</DL>
|
|
<P>
|
|
|
|
Programs based on the X Toolkit Intrinsics
|
|
obtain resources from the following sources
|
|
(other programs usually support some subset of these sources):
|
|
<DL COMPACT>
|
|
<DT id="38"><B>RESOURCE_MANAGER root window property</B>
|
|
|
|
<DD>
|
|
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 <I>xrdb</I> program.
|
|
This is frequently taken care
|
|
of when the user starts up X through the display manager or <I>xinit</I>.
|
|
<DT id="39"><B>SCREEN_RESOURCES root window property</B>
|
|
|
|
<DD>
|
|
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 <I>xrdb</I> program will sort resources automatically and place them
|
|
in RESOURCE_MANAGER or SCREEN_RESOURCES, as appropriate.
|
|
<DT id="40"><B>application-specific files</B>
|
|
|
|
<DD>
|
|
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/share/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/share/X11/app-defaults/.
|
|
See the <I>X Toolkit Intrinsics - C Language Interface</I> manual for
|
|
details.
|
|
<DT id="41"><B>XENVIRONMENT</B>
|
|
|
|
<DD>
|
|
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 <I>$HOME</I>/.Xdefaults-<I>hostname</I> is looked for instead,
|
|
where <I>hostname</I> is the name of the host where the application
|
|
is executing.
|
|
<DT id="42"><B>-xrm </B><I>resourcestring</I>
|
|
|
|
<DD>
|
|
Resources can also be specified from the
|
|
command line. The <I>resourcestring</I> 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 <B>-xrm</B> arguments may be given on the
|
|
command line.
|
|
</DL>
|
|
<P>
|
|
|
|
Program resources are organized into groups called <I>classes</I>, so that
|
|
collections of individual resources (each of which are
|
|
called <I>instances</I>)
|
|
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:
|
|
<P>
|
|
|
|
<DL COMPACT>
|
|
<DT id="43"><B>background (</B>class<B> Background)</B>
|
|
|
|
<DD>
|
|
This resource specifies the color to use for the window background.
|
|
</DL>
|
|
<P>
|
|
|
|
<DL COMPACT>
|
|
<DT id="44"><B>borderWidth (</B>class<B> BorderWidth)</B>
|
|
|
|
<DD>
|
|
This resource specifies the width in pixels of the window border.
|
|
</DL>
|
|
<P>
|
|
|
|
<DL COMPACT>
|
|
<DT id="45"><B>borderColor (</B>class<B> BorderColor)</B>
|
|
|
|
<DD>
|
|
This resource specifies the color to use for the window border.
|
|
</DL>
|
|
<P>
|
|
|
|
Most applications using the X Toolkit Intrinsics also have the resource
|
|
<B>foreground</B>
|
|
(class <B>Foreground</B>), specifying the color to use for text
|
|
and graphics within the window.
|
|
<P>
|
|
|
|
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,
|
|
<P>
|
|
<PRE>
|
|
bitmap*Dashed: off
|
|
XTerm*cursorColor: gold
|
|
XTerm*multiScroll: on
|
|
XTerm*jumpScroll: on
|
|
XTerm*reverseWrap: on
|
|
XTerm*curses: on
|
|
XTerm*Font: 6x10
|
|
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
|
|
XTerm*titeInhibit: on
|
|
XTerm*ttyModes: intr ^c erase ^? kill ^u
|
|
XLoad*Background: gold
|
|
XLoad*Foreground: red
|
|
XLoad*highlight: black
|
|
XLoad*borderWidth: 0
|
|
emacs*Geometry: 80x65-0-0
|
|
emacs*Background: rgb:5b/76/86
|
|
emacs*Foreground: white
|
|
emacs*Cursor: white
|
|
emacs*BorderColor: white
|
|
emacs*Font: 6x10
|
|
xmag*geometry: -0-0
|
|
xmag*borderColor: white
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
If these resources were stored in a file called <I>.Xresources</I> in your home
|
|
directory, they could be added to any existing resources in the server with
|
|
the following command:
|
|
<P>
|
|
<PRE>
|
|
% xrdb -merge $HOME/.Xresources
|
|
</PRE>
|
|
|
|
<P>
|
|
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 <I>Xlib</I>
|
|
manual section <I>Resource Manager Functions</I> for more information.
|
|
<A NAME="lbAP"> </A>
|
|
<H2>ENVIRONMENT</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="46"><B>DISPLAY</B>
|
|
|
|
<DD>
|
|
This is the only mandatory environment variable. It must point to an
|
|
X server. See section "Display Names" above.
|
|
<DT id="47"><B>XAUTHORITY</B>
|
|
|
|
<DD>
|
|
This must point to a file that contains authorization data. The default
|
|
is <I>$HOME/.Xauthority</I>. See
|
|
<B><A HREF="/cgi-bin/man/man2html?7+Xsecurity">Xsecurity</A></B>(7),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xauth">xauth</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xdm">xdm</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?3+Xau">Xau</A></B>(3).
|
|
|
|
<DT id="48"><B>ICEAUTHORITY</B>
|
|
|
|
<DD>
|
|
This must point to a file that contains authorization data. The default
|
|
is <I>$HOME/.ICEauthority</I>.
|
|
<DT id="49"><B>LC_ALL</B>, <B>LC_CTYPE</B>, <B>LANG</B>
|
|
|
|
<DD>
|
|
The first non-empty value among these three determines the current
|
|
locale's facet for character handling, and in particular the default
|
|
text encoding. See
|
|
<B><A HREF="/cgi-bin/man/man2html?7+locale">locale</A></B>(7),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?3+setlocale">setlocale</A></B>(3),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+locale">locale</A></B>(1).
|
|
|
|
<DT id="50"><B>XMODIFIERS</B>
|
|
|
|
<DD>
|
|
This variable can be set to contain additional information important
|
|
for the current locale setting. Typically set to <I>@im=<input-method></I>
|
|
to enable a particular input method. See
|
|
<B><A HREF="/cgi-bin/man/man2html?3+XSetLocaleModifiers">XSetLocaleModifiers</A></B>(3).
|
|
|
|
<DT id="51"><B>XLOCALEDIR</B>
|
|
|
|
<DD>
|
|
This must point to a directory containing the locale.alias file and
|
|
Compose and XLC_LOCALE file hierarchies for all locales. The default value
|
|
is<I> /usr/share/X11/locale</I>.
|
|
<DT id="52"><B>XENVIRONMENT</B>
|
|
|
|
<DD>
|
|
This must point to a file containing X resources. The default is
|
|
<I>$HOME/.Xdefaults-<hostname></I>. Unlike <I>$HOME/.Xresources</I>,
|
|
it is consulted each time an X application starts.
|
|
<DT id="53"><B>XFILESEARCHPATH</B>
|
|
|
|
<DD>
|
|
This must contain a colon separated list of path templates, where libXt
|
|
will search for resource files. The default value consists of
|
|
<P>
|
|
<PRE>
|
|
/etc/X11/%L/%T/%N%C%S:\
|
|
/etc/X11/%l/%T/%N%C%S:\
|
|
/etc/X11/%T/%N%C%S:\
|
|
/etc/X11/%L/%T/%N%S:\
|
|
/etc/X11/%l/%T/%N%S:\
|
|
/etc/X11/%T/%N%S:\
|
|
/usr/share/X11/%L/%T/%N%C%S:\
|
|
/usr/share/X11/%l/%T/%N%C%S:\
|
|
/usr/share/X11/%T/%N%C%S:\
|
|
/usr/share/X11/%L/%T/%N%S:\
|
|
/usr/share/X11/%l/%T/%N%S:\
|
|
/usr/share/X11/%T/%N%S:\
|
|
/usr/lib/x86_64-linux-gnu/X11/%L/%T/%N%C%S:\
|
|
/usr/lib/x86_64-linux-gnu/X11/%l/%T/%N%C%S:\
|
|
/usr/lib/x86_64-linux-gnu/X11/%T/%N%C%S:\
|
|
/usr/lib/x86_64-linux-gnu/X11/%L/%T/%N%S:\
|
|
/usr/lib/x86_64-linux-gnu/X11/%l/%T/%N%S:\
|
|
/usr/lib/x86_64-linux-gnu/X11/%T/%N%S
|
|
</PRE>
|
|
|
|
<P>
|
|
A path template is transformed to a pathname by substituting:
|
|
<P>
|
|
<PRE>
|
|
%D => the implementation-specific default path
|
|
%N => name (basename) being searched for
|
|
%T => type (dirname) being searched for
|
|
%S => suffix being searched for
|
|
%C => value of the resource "customization"
|
|
(class "Customization")
|
|
%L => the locale name
|
|
%l => the locale's language (part before '_')
|
|
%t => the locale's territory (part after '_` but before '.')
|
|
%c => the locale's encoding (part after '.')
|
|
</PRE>
|
|
|
|
<DT id="54"><B>XUSERFILESEARCHPATH</B>
|
|
|
|
<DD>
|
|
This must contain a colon separated list of path templates,
|
|
where libXt will search for user dependent resource files. The default
|
|
value is:
|
|
<P>
|
|
<PRE>
|
|
$XAPPLRESDIR/%L/%N%C:\
|
|
$XAPPLRESDIR/%l/%N%C:\
|
|
$XAPPLRESDIR/%N%C:\
|
|
$HOME/%N%C:\
|
|
$XAPPLRESDIR/%L/%N:\
|
|
$XAPPLRESDIR/%l/%N:\
|
|
$XAPPLRESDIR/%N:\
|
|
$HOME/%N
|
|
</PRE>
|
|
|
|
<P>
|
|
$XAPPLRESDIR defaults to <I>$HOME</I>, see below.
|
|
<P>
|
|
A path template is transformed to a pathname by substituting:
|
|
<P>
|
|
<PRE>
|
|
%D => the implementation-specific default path
|
|
%N => name (basename) being searched for
|
|
%T => type (dirname) being searched for
|
|
%S => suffix being searched for
|
|
%C => value of the resource "customization"
|
|
(class "Customization")
|
|
%L => the locale name
|
|
%l => the locale's language (part before '_')
|
|
%t => the locale's territory (part after '_` but before '.')
|
|
%c => the locale's encoding (part after '.')
|
|
</PRE>
|
|
|
|
<DT id="55"><B>XAPPLRESDIR</B>
|
|
|
|
<DD>
|
|
This must point to a base directory where the user stores the application
|
|
dependent resource files. The default value is <I>$HOME</I>. Only used if
|
|
XUSERFILESEARCHPATH is not set.
|
|
<DT id="56"><B>XKEYSYMDB</B>
|
|
|
|
<DD>
|
|
This must point to a file containing nonstandard keysym definitions.
|
|
The default value is<I> /usr/share/X11/XKeysymDB</I>.
|
|
<DT id="57"><B>XCMSDB</B>
|
|
|
|
<DD>
|
|
This must point to a color name database file. The default value is
|
|
<I> /usr/lib/x86_64-linux-gnu/X11/Xcms.txt</I>.
|
|
<DT id="58"><B>RESOURCE_NAME</B>
|
|
|
|
<DD>
|
|
This serves as main identifier for resources belonging to the program
|
|
being executed. It defaults to the basename of pathname of the program.
|
|
<DT id="59"><B>SESSION_MANAGER</B>
|
|
|
|
<DD>
|
|
Denotes the session manager to which the application should connect. See
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xsm">xsm</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+rstart">rstart</A></B>(1).
|
|
|
|
<DT id="60"><B>XF86BIGFONT_DISABLE</B>
|
|
|
|
<DD>
|
|
Setting this variable to a non-empty value disables the XFree86-Bigfont
|
|
extension. This extension is a mechanism to reduce the memory consumption
|
|
of big fonts by use of shared memory.
|
|
</DL>
|
|
<P>
|
|
|
|
<B>XKB_FORCE</B>
|
|
|
|
<BR>
|
|
|
|
<B>XKB_DISABLE</B>
|
|
|
|
<BR>
|
|
|
|
<B>XKB_DEBUG</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_CHARSET</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_LOCALE_CHARSETS</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_OPTIONS_ENABLE</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_LATIN1_LOOKUP</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_CONSUME_LOOKUP_MODS</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_CONSUME_SHIFT_AND_LOCK</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_IGNORE_NEW_KEYBOARDS</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_CONTROL_FALLBACK</B>
|
|
|
|
<BR>
|
|
|
|
<B>_XKB_COMP_LED</B>
|
|
|
|
<B>_XKB_COMP_FAIL_BEEP</B>
|
|
|
|
<P>
|
|
|
|
These variables influence the X Keyboard Extension.
|
|
<A NAME="lbAQ"> </A>
|
|
<H2>EXAMPLES</H2>
|
|
|
|
The following is a collection of sample command lines for some of the
|
|
more frequently used commands. For more information on a particular command,
|
|
please refer to that command's manual page.
|
|
<P>
|
|
<PRE>
|
|
% xrdb $HOME/.Xresources
|
|
% xmodmap -e "keysym BackSpace = Delete"
|
|
% mkfontdir /usr/local/lib/X11/otherfonts
|
|
% xset fp+ /usr/local/lib/X11/otherfonts
|
|
% xmodmap $HOME/.keymap.km
|
|
% xsetroot -solid 'rgbi:.8/.8/.8'
|
|
% xset b 100 400 c 50 s 1800 r on
|
|
% xset q
|
|
% twm
|
|
% xmag
|
|
% xclock -geometry 48x48-0+0 -bg blue -fg white
|
|
% xeyes -geometry 48x48-48+0
|
|
% xbiff -update 20
|
|
% xlsfonts '*helvetica*'
|
|
% xwininfo -root
|
|
% xdpyinfo -display joesworkstation:0
|
|
% xhost -joesworkstation
|
|
% xrefresh
|
|
% xwd | xwud
|
|
% bitmap companylogo.bm 32x32
|
|
% xcalc -bg blue -fg magenta
|
|
% xterm -geometry 80x66-0-0 -name myxterm $*
|
|
</PRE>
|
|
|
|
<A NAME="lbAR"> </A>
|
|
<H2>DIAGNOSTICS</H2>
|
|
|
|
A wide variety of error messages are generated from various programs.
|
|
The default error handler in <I>Xlib</I> (also used by many toolkits) uses
|
|
standard resources to construct diagnostic messages when errors occur. The
|
|
defaults for these messages are usually stored in
|
|
<I>/usr/share/X11/XErrorDB</I>. If this file is not present,
|
|
error messages will be rather terse and cryptic.
|
|
<P>
|
|
|
|
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
|
|
<I>StringConversionWarnings</I> resource.
|
|
<P>
|
|
|
|
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 <I>xrdb</I> program (frequently called <I>.Xresources</I>
|
|
or <I>.Xres</I> in the user's home directory):
|
|
<P>
|
|
<PRE>
|
|
*StringConversionWarnings: on
|
|
</PRE>
|
|
|
|
<P>
|
|
To have conversion messages printed for just a particular application,
|
|
the appropriate instance name can be placed before the asterisk:
|
|
<P>
|
|
<PRE>
|
|
xterm*StringConversionWarnings: on
|
|
</PRE>
|
|
|
|
<A NAME="lbAS"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<P>
|
|
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?7+XOrgFoundation">XOrgFoundation</A></B>(7),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?7+XStandards">XStandards</A></B>(7),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?7+Xsecurity">Xsecurity</A></B>(7),
|
|
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+appres">appres</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+bdftopcf">bdftopcf</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+bitmap">bitmap</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+editres">editres</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+fsinfo">fsinfo</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+fslsfonts">fslsfonts</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+fstobdf">fstobdf</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+iceauth">iceauth</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+imake">imake</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+makedepend">makedepend</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+mkfontdir">mkfontdir</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+oclock">oclock</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+proxymngr">proxymngr</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+rgb">rgb</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+resize">resize</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+rstart">rstart</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+smproxy">smproxy</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+twm">twm</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+x11perf">x11perf</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+x11perfcomp">x11perfcomp</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xauth">xauth</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xclipboard">xclipboard</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xclock">xclock</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xcmsdb">xcmsdb</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xconsole">xconsole</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xdm">xdm</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xdpyinfo">xdpyinfo</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xfd">xfd</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xfindproxy">xfindproxy</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xfs">xfs</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xfwp">xfwp</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xhost">xhost</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xinit">xinit</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xkbbell">xkbbell</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xkbcomp">xkbcomp</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xkbevd">xkbevd</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xkbprint">xkbprint</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xkbvleds">xkbvleds</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xkbwatch">xkbwatch</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xkill">xkill</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xlogo">xlogo</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xlsatoms">xlsatoms</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xlsclients">xlsclients</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xlsfonts">xlsfonts</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xmag">xmag</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xmh">xmh</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xmodmap">xmodmap</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xprop">xprop</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xrdb">xrdb</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xrefresh">xrefresh</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xrx">xrx</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xset">xset</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xsetroot">xsetroot</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xsm">xsm</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xstdcmap">xstdcmap</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xterm">xterm</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xwd">xwd</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xwininfo">xwininfo</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+xwud">xwud</A></B>(1).
|
|
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xserver">Xserver</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xorg">Xorg</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xdmx">Xdmx</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xephyr">Xephyr</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xnest">Xnest</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xquartz">Xquartz</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xvfb">Xvfb</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+Xvnc">Xvnc</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+XWin">XWin</A></B>(1).
|
|
|
|
|
|
<I>Xlib - C Language X Interface</I>,
|
|
|
|
and
|
|
<I>X Toolkit Intrinsics - C Language Interface</I>
|
|
|
|
<A NAME="lbAT"> </A>
|
|
<H2>TRADEMARKS</H2>
|
|
|
|
<P>
|
|
|
|
X Window System is a trademark of The Open Group.
|
|
<A NAME="lbAU"> </A>
|
|
<H2>AUTHORS</H2>
|
|
|
|
<P>
|
|
|
|
A cast of thousands, literally. Releases 6.7 and later are
|
|
brought to you by the X.Org Foundation. The names of all people who
|
|
made it a reality will be found in the individual documents and
|
|
source files.
|
|
<P>
|
|
|
|
Releases 6.6 and 6.5 were done by The X.Org Group. Release 6.4 was done by
|
|
The X Project Team. The Release 6.3 distribution was from The X Consortium,
|
|
Inc. The staff members at the X Consortium responsible for that release
|
|
were: Donna Converse (emeritus), Stephen Gildea (emeritus), Kaleb Keithley,
|
|
Matt Landau (emeritus), Ralph Mor (emeritus), Janet O'Halloran, Bob
|
|
Scheifler, Ralph Swick, Dave Wiggins (emeritus), and Reed Augliere.
|
|
<P>
|
|
|
|
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.
|
|
X Consortium, Inc. closed its doors on December 31, 1996. All rights to the
|
|
X Window System have been assigned to The Open Group.
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="61"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="62"><A HREF="#lbAC">OVERVIEW</A><DD>
|
|
<DT id="63"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="64"><A HREF="#lbAE">STARTING UP</A><DD>
|
|
<DT id="65"><A HREF="#lbAF">DISPLAY NAMES</A><DD>
|
|
<DT id="66"><A HREF="#lbAG">ACCESS CONTROL</A><DD>
|
|
<DT id="67"><A HREF="#lbAH">GEOMETRY SPECIFICATIONS</A><DD>
|
|
<DT id="68"><A HREF="#lbAI">WINDOW MANAGERS</A><DD>
|
|
<DT id="69"><A HREF="#lbAJ">FONT NAMES</A><DD>
|
|
<DT id="70"><A HREF="#lbAK">FONT SERVER NAMES</A><DD>
|
|
<DT id="71"><A HREF="#lbAL">COLOR NAMES</A><DD>
|
|
<DT id="72"><A HREF="#lbAM">KEYBOARDS</A><DD>
|
|
<DT id="73"><A HREF="#lbAN">OPTIONS</A><DD>
|
|
<DT id="74"><A HREF="#lbAO">RESOURCES</A><DD>
|
|
<DT id="75"><A HREF="#lbAP">ENVIRONMENT</A><DD>
|
|
<DT id="76"><A HREF="#lbAQ">EXAMPLES</A><DD>
|
|
<DT id="77"><A HREF="#lbAR">DIAGNOSTICS</A><DD>
|
|
<DT id="78"><A HREF="#lbAS">SEE ALSO</A><DD>
|
|
<DT id="79"><A HREF="#lbAT">TRADEMARKS</A><DD>
|
|
<DT id="80"><A HREF="#lbAU">AUTHORS</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:06:10 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|