


X(1)                                                                     X(1)



NAME
  X - a portable, network-transparent window system

SYNOPSIS

  The X Window System is a network transparent window system developed at MIT
  which runs on a wide range of computing and graphics machines.  It should
  be relatively straightforward to build the MIT 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
                                      X11

  _X _W_i_n_d_o_w _S_y_s_t_e_m is a trademark of the Massachusetts Institute of Technol-
  ogy.

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 chan-
  nels.  Although the most common case is for the client programs to be run-
  ning 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 opera-
  tions, on both monochrome and color displays.  For a full explanation of
  the functions that are available, see the _X_l_i_b - _C _L_a_n_g_u_a_g_e _X _I_n_t_e_r_f_a_c_e
  manual, the _X _W_i_n_d_o_w _S_y_s_t_e_m _P_r_o_t_o_c_o_l specification, the _X _T_o_o_l_k_i_t _I_n_t_r_i_n_-
  _s_i_c_s - _C _L_a_n_g_u_a_g_e _I_n_t_e_r_f_a_c_e manual, and various toolkit documents.

  The number of programs that use _X is quite large.  Programs provided in the
  core MIT distribution include: a terminal emulator (_x_t_e_r_m), a window
  manager (_t_w_m), a display manager (_x_d_m), a console redirect program (_x_c_o_n_-
  _s_o_l_e), mail managing utilities (_x_m_h and _x_b_i_f_f), a manual page browser
  (_x_m_a_n), a bitmap editor (_b_i_t_m_a_p), a resource editor (_e_d_i_t_r_e_s), a ditroff
  previewer (_x_d_i_t_v_i_e_w), access control programs (_x_a_u_t_h and _x_h_o_s_t), user
  preference setting programs (_x_r_d_b, _x_c_m_s_d_b, _x_s_e_t, _x_s_e_t_r_o_o_t, _x_s_t_d_c_m_a_p, and
  _x_m_o_d_m_a_p), a load monitor (_x_l_o_a_d), clocks (_x_c_l_o_c_k and _o_c_l_o_c_k), a font
  displayer (_x_f_d), utilities for listing information about fonts, windows,
  and displays (_x_l_s_f_o_n_t_s, _x_f_o_n_t_s_e_l, _x_w_i_n_i_n_f_o, _x_l_s_c_l_i_e_n_t_s, _x_d_p_y_i_n_f_o, and
  _x_p_r_o_p), a diagnostic for seeing what events are generated and when (_x_e_v),
  screen image manipulation utilities (_x_w_d, _x_w_u_d, _x_p_r, and _x_m_a_g), and various
  demos (_x_e_y_e_s, _i_c_o, _x_g_c, _x_1_1_p_e_r_f, etc.).


  Many other utilities, window managers, games, toolkits, etc. are included
  as user-contributed software in the MIT 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 on whether or not you use other window
  systems in addition to X.

  _x_d_m ((tthhee XX DDiissppllaayy MMaannaaggeerr))
          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
          _x_d_m.  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 _x_d_m, 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, _x_d_m
          will display an error message and ask you to try again.  After you
          have successfully logged in, _x_d_m will start up your X environment.
          By default, if you have an executable file named ._x_s_e_s_s_i_o_n in your
          home directory, _x_d_m 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 back-
          ground, the speed of the pointer, etc.).  Your site administrator
          can provide details.

  _x_i_n_i_t ((rruunn mmaannuuaallllyy ffrroomm tthhee sshheellll))
          Sites that support more than one window system might choose to use
          the _x_i_n_i_t 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 start-
          ing several terminal emulators) in a nice way.  If not, you can
          build such a script using the _x_i_n_i_t 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 fin-
          ish.  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, _x_i_n_i_t is not intended for end
          users.

DISPLAY NAMES

  From the user's prospective, every X server has a _d_i_s_p_l_a_y _n_a_m_e of the form:

                      _h_o_s_t_n_a_m_e:_d_i_s_p_l_a_y_n_u_m_b_e_r._s_c_r_e_e_n_n_u_m_b_e_r

  This information is used by the application to determine how it should con-
  nect to the server and which screen it should use by default (on displays
  with multiple monitors):

  _h_o_s_t_n_a_m_e
          The _h_o_s_t_n_a_m_e 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.

  _d_i_s_p_l_a_y_n_u_m_b_e_r
          The phrase "display" is usually used to refer to collection of mon-
          itors 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,
          will 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 _d_i_s_p_l_a_y _n_u_m_b_e_r (beginning at 0)
          when the X server for that display is started.  The display number
          must always be given in a display name.

  _s_c_r_e_e_n_n_u_m_b_e_r
          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 _s_c_r_e_e_n _n_u_m_b_e_r (beginning at 0) when the X
          server for that display is started.  If the screen number is not
          given, then 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 _x_t_e_r_m ter-
  minal emulator.  However, when you log into another machine on a network,
  you'll need to set DISPLAY by hand to point to your display.  For example,

      % setenv DISPLAY myws:0
      $ DISPLAY=myws:0; export DISPLAY
  The _x_o_n 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 --ddiissppllaayy _d_i_s_p_l_a_y_-
  _n_a_m_e to temporarily override the contents of DISPLAY.  This is most com-
  monly 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 _h_o_s_t_n_a_m_e part of the
  display name is used to determine the type of channel (also called a tran-
  sport layer) to be used.  X servers generally support the following types
  of connections:

  _l_o_c_a_l
          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.

  _T_C_P/_I_P
          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:
          _e_x_p_o._l_c_s._m_i_t._e_d_u:_0, _e_x_p_o:_0, _1_8._3_0._0._2_1_2:_0, _b_i_g_m_a_c_h_i_n_e:_1, and
          _h_y_d_r_a:_0._1.

  _D_E_C_n_e_t
          The hostname part of the display name should be the server
          machine's nodename followed by two colons instead of one.  For
          example:  _m_y_w_s::_0, _b_i_g::_1, and _h_y_d_r_a::_0._1.

ACCESS CONTROL
  An X server can use several types of access control.  Mechanisms provided
  in Release 5 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.

  _X_d_m initializes access control for the server, and also places authoriza-
  tion 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 _x_h_o_s_t), the server no longer
  performs any authorization on connections from those machines.  Be careful
  with this.

  The file from which _X_l_i_b extracts authorization data can be specified with
  the environment variable XXAAUUTTHHOORRIITTYY, and defaults to the file ..XXaauutthhoorriittyy
  in the home directory.  _X_d_m uses $$HHOOMMEE//..XXaauutthhoorriittyy 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, then 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 _x_a_u_t_h.  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 _f_t_p or
  _r_c_p 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 particu-
  lar authorization data to know if this is actually a problem.

  For more information on access control, see the _X_s_e_c_u_r_i_t_y manual page.

GEOMETRY SPECIFICATIONS
  One of the advantages of using window systems instead of hardwired termi-
  nals 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
  --ggeeoommeettrryy _W_I_D_T_H_x_H_E_I_G_H_T+_X_O_F_F+_Y_O_F_F (where _W_I_D_T_H, _H_E_I_G_H_T, _X_O_F_F, and _Y_O_F_F are
  numbers) for specifying a preferred size and location for this
  application's main window.

  The _W_I_D_T_H and _H_E_I_G_H_T parts of the geometry specification are usually meas-
  ured in either pixels or characters, depending on the application.  The
  _X_O_F_F and _Y_O_F_F parts are measured in pixels and are used to specify the dis-
  tance 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 indi-
  cated edge of the screen to the corresponding edge of the window.  The X
  offset may be specified in the following ways:

  +_X_O_F_F   The left edge of the window is to be placed _X_O_F_F pixels in from the
          left edge of the screen (i.e. the X coordinate of the window's ori-
          gin will be _X_O_F_F).  _X_O_F_F may be negative, in which case the
          window's left edge will be off the screen.

  -_X_O_F_F   The right edge of the window is to be placed _X_O_F_F pixels in from
          the right edge of the screen.  _X_O_F_F may be negative, in which case
          the window's right edge will be off the screen.

  The Y offset has similar meanings:

  +_Y_O_F_F   The top edge of the window is to be _Y_O_F_F pixels below the top edge
          of the screen (i.e. the Y coordinate of the window's origin will be
          _Y_O_F_F).  _Y_O_F_F may be negative, in which case the window's top edge
          will be off the screen.

  -_Y_O_F_F   The bottom edge of the window is to be _Y_O_F_F pixels above the bottom
          edge of the screen.  _Y_O_F_F 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
  _X_O_F_F or _Y_O_F_F 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 will be placed in roughly
  the center of the screen and a load average monitor, mailbox, and clock
  will be placed in the upper right hand corner:

      xterm -fn 6x10 -geometry 80x24+30+200 &
      xclock -geometry 48x48-0+0 &
      xload -geometry 48x48-96+0 &
      xbiff -geometry 48x48-48+0 &

WINDOW MANAGERS
  The layout of windows on the screen is controlled by special programs
  called _w_i_n_d_o_w _m_a_n_a_g_e_r_s.  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 MIT distribution
  comes with a window manager named _t_w_m 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 win-
  dows).

  See the user-contributed software in the MIT distribution for other popular
  window managers.

FONT NAMES
  Collections of characters for displaying text and symbols in X are known as
  _f_o_n_t_s.  A font typically contains images that share a common appearance and
  look nice together (for example, a single size, boldness, slant, and char-
  acter 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 _f_a_m_i_l_i_e_s.

  Fonts come in various sizes.  The X server supports _s_c_a_l_a_b_l_e fonts, meaning
  it is possible to create a font of arbitrary size from a single source for
  the font.  The server supports scaling from _o_u_t_l_i_n_e fonts and _b_i_t_m_a_p 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 _f_o_n_t _p_a_t_h.  Although most
  installations will choose to have the server start up with all of the com-
  monly used font directories in the font path, the font path can be changed
  at any time with the _x_s_e_t program.  However, it is important to remember
  that the directory names are on the sseerrvveerr's machine, not on the
  application's.  The most common fonts use by X servers and font servers can
  be found in four directories:

  /_u_s_r/_l_i_b/_X_1_1/_f_o_n_t_s/_m_i_s_c
          This directory contains many miscellaneous bitmap fonts that are
          useful on all systems.  It contains a family of fixed-width fonts,
          a family of fixed-width fonts from Dale Schumacher, several Kana
          fonts from Sony Corporation, two JIS Kanji fonts, two Hangul fonts
          from Daewoo Electronics, two Hebrew fonts from Joseph Friedman, the
          standard cursor font, two cursor fonts from Digital Equipment
          Corporation, and cursor and glyph fonts from Sun Microsystems.  It
          also has various font name aliases for the fonts, including ffiixxeedd
          and vvaarriiaabbllee.

  /_u_s_r/_l_i_b/_X_1_1/_f_o_n_t_s/_S_p_e_e_d_o
          This directory contains outline fonts for Bitstream's Speedo
          rasterizer.  A single font face, in normal, bold, italic, and bold
          italic, is provided, contributed by Bitstream, Inc.

  /_u_s_r/_l_i_b/_X_1_1/_f_o_n_t_s/_7_5_d_p_i
          This directory contains bitmap fonts contributed by Adobe Systems,
          Inc., Digital Equipment Corporation, Bitstream, Inc., Bigelow and
          Holmes, and Sun Microsystems, Inc.  for 75 dots per inch displays.
          An integrated selection of sizes, styles, and weights are provided
          for each family.

  /_u_s_r/_l_i_b/_X_1_1/_f_o_n_t_s/_1_0_0_d_p_i
          This directory contains 100 dots per inch versions of some of the
          fonts in the _7_5_d_p_i directory.

  Bitmap font files are usually created by compiling a textual font descrip-
  tion into binary form, using _b_d_f_t_o_p_c_f.  Font databases are created by run-
  ning the _m_k_f_o_n_t_d_i_r program in the directory containing the source or com-
  piled versions of the fonts.  Whenever fonts are added to a directory,
  _m_k_f_o_n_t_d_i_r 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 _x_s_e_t
  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 _x_f_o_n_t_s_e_l and _x_l_s_f_o_n_t_s 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.  How-
  ever, the X server supports wildcarding of font names, so the full specifi-
  cation

      -_a_d_o_b_e-_c_o_u_r_i_e_r-_m_e_d_i_u_m-_r-_n_o_r_m_a_l--_1_0-_1_0_0-_7_5-_7_5-_m-_6_0-_i_s_o_8_8_5_9-_1

  might be abbreviated as:

      -*-_c_o_u_r_i_e_r-_m_e_d_i_u_m-_r-_n_o_r_m_a_l--*-_1_0_0-*-*-*-*-_i_s_o_8_8_5_9-_1

  Because the shell also has special meanings for * and ?, wildcarded font
  names should be quoted:

      % xlsfonts -fn '-*-courier-medium-r-normal--*-100-*-*-*-*-*-*'

  The _x_l_s_f_o_n_t_s 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-_7_5-_7_5-*-_0-*-*
      -*-*-*-*-*-*-_0-_0-_1_0_0-_1_0_0-*-_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 con-
  taining 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, meas-
  ured 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/_h_o_s_t_n_a_m_e:_p_o_r_t
      tcp/_h_o_s_t_n_a_m_e:_p_o_r_t/_c_a_t_a_l_o_g_u_e_l_i_s_t

  The _h_o_s_t_n_a_m_e specifies the name (or decimal numeric address) of the machine
  on which the font server is running.  The _p_o_r_t is the decimal TCP port on
  which the font server is listening for connections.  The _c_a_t_a_l_o_g_u_e_l_i_s_t
  specifies a list of catalogue names, with '+' as a separator.

  Examples: _t_c_p/_e_x_p_o._l_c_s._m_i_t._e_d_u:_7_0_0_0, _t_c_p/_1_8._3_0._0._2_1_2:_7_0_0_1/_a_l_l.

  One of the following forms can be used to name a font server that accepts
  DECnet connections:

      decnet/_n_o_d_e_n_a_m_e::font$_o_b_j_n_a_m_e
      decnet/_n_o_d_e_n_a_m_e::font$_o_b_j_n_a_m_e/_c_a_t_a_l_o_g_u_e_l_i_s_t

  The _n_o_d_e_n_a_m_e specifies the name (or decimal numeric address) of the machine
  on which the font server is running.  The _o_b_j_n_a_m_e is a normal, case-
  insensitive DECnet object name.  The _c_a_t_a_l_o_g_u_e_l_i_s_t specifies a list of
  catalogue names, with '+' as a separator.

  Examples: _D_E_C_n_e_t/_S_R_V_N_O_D::_F_O_N_T$_D_E_F_A_U_L_T, _d_e_c_n_e_t/_4_4._7_0::_f_o_n_t$_s_p_e_c_i_a_l/_s_y_m_b_o_l_s.

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 specifi-
  cation can identify a color in either device-dependent (RGB) or device-
  independent terms.  Color strings are case-insensitive.

  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.  _X_l_i_b 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 /_u_s_r/_l_i_b/_X_1_1/_r_g_b._t_x_t.

  A numerical color specification consists of a color space name and a set of
  values in the following syntax:

      <_c_o_l_o_r__s_p_a_c_e__n_a_m_e>:<_v_a_l_u_e>/.../<_v_a_l_u_e>

  An RGB Device specification is identified by the prefix "rgb:" and has the
  following syntax:

      rgb:<_r_e_d>/<_g_r_e_e_n>/<_b_l_u_e>

          <_r_e_d>, <_g_r_e_e_n>, <_b_l_u_e> := _h | _h_h | _h_h_h | _h_h_h_h
          _h := single hexadecimal digits
  Note that _h indicates the value scaled in 4 bits, _h_h the value scaled in 8
  bits, _h_h_h the value scaled in 12 bits, and _h_h_h_h 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:<_r_e_d>/<_g_r_e_e_n>/<_b_l_u_e>

  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 _X_l_i_b 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.

  The standard device-independent string specifications have the following
  syntax:

      CIEXYZ:<_X>/<_Y>/<_Z>             (_n_o_n_e, 1, _n_o_n_e)
      CIEuvY:<_u>/<_v>/<_Y>             (~.6, ~.6, 1)
      CIExyY:<_x>/<_y>/<_Y>             (~.75, ~.85, 1)
      CIELab:<_L>/<_a>/<_b>             (100, _n_o_n_e, _n_o_n_e)
      CIELuv:<_L>/<_u>/<_v>             (100, _n_o_n_e, _n_o_n_e)
      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 possi-
  bly 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 _X_l_i_b reference
  manual.



KEYBOARDS

  The X keyboard model is broken into two layers:  server-specific codes
  (called _k_e_y_c_o_d_e_s) which represent the physical keys, and server-independent
  symbols (called _k_e_y_s_y_m_s) which represent the letters or words that appear
  on the keys. Two tables are kept in the server for converting keycodes to
  keysyms:

  _m_o_d_i_f_i_e_r _l_i_s_t
          Some keys (such as Shift, Control, and Caps Lock) are known as
          _m_o_d_i_f_i_e_r 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.  When-
          ever a key is pressed or released, the server generates an _e_v_e_n_t
          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.

  _k_e_y_m_a_p _t_a_b_l_e
          Applications translate event keycodes and modifier masks into
          keysyms using a _k_e_y_s_y_m _t_a_b_l_e which contains one row for each key-
          code and one column for various modifier states.  This table is
          initialized by the server to correspond to normal typewriter con-
          ventions.  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 the second element is the special keysym _N_o_S_y_m_b_o_l, 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 Mod1 through Mod5.  This modifier is called the ``group modif-
  ier.'' 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 alpha-
  betic, 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 automat-
  ically accept the following options:

  --ddiissppllaayy _d_i_s_p_l_a_y
          This option specifies the name of the X server to use.

  --ggeeoommeettrryy _g_e_o_m_e_t_r_y
          This option specifies the initial size and location of the window.

  --bbgg _c_o_l_o_r,, --bbaacckkggrroouunndd _c_o_l_o_r
          Either option specifies the color to use for the window background.

  --bbdd _c_o_l_o_r,, --bboorrddeerrccoolloorr _c_o_l_o_r
          Either option specifies the color to use for the window border.

  --bbww _n_u_m_b_e_r,, --bboorrddeerrwwiiddtthh _n_u_m_b_e_r
          Either option specifies the width in pixels of the window border.

  --ffgg _c_o_l_o_r,, --ffoorreeggrroouunndd _c_o_l_o_r
          Either option specifies the color to use for text or graphics.

  --ffnn _f_o_n_t,, --ffoonntt _f_o_n_t
          Either option specifies the font to use for displaying text.

  --iiccoonniicc
          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.

  --nnaammee
          This option specifies the name under which resources for the appli-
          cation should be found.  This option is useful in shell aliases to
          distinguish between invocations of an application, without resort-
          ing to creating links to alter the executable file name.

  --rrvv, --rreevveerrssee
          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.

  ++rrvv
          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.

  --sseelleeccttiioonnTTiimmeeoouutt
          This option specifies the timeout in milliseconds within which two
          communicating applications must respond to one another for a selec-
          tion request.

  --ssyynncchhrroonnoouuss
          This option indicates that requests to the X server should be sent
          synchronously, instead of asynchronously.  Since _X_l_i_b 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.

  --ttiittllee _s_t_r_i_n_g
          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.

  --xxnnllllaanngguuaaggee _l_a_n_g_u_a_g_e[__t_e_r_r_i_t_o_r_y][._c_o_d_e_s_e_t]
          This option specifies the language, territory, and codeset for use
          in resolving resource and other filenames.

  --xxrrmm _r_e_s_o_u_r_c_e_s_t_r_i_n_g
          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. _B_i_t_m_a_p or _E_m_a_c_s) although some programs
  that begin with the letter ``x'' also capitalize the second letter for his-
  torical 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 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>}

  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 Resour-
  ceName.  If a resource file contains multiple lines with the same Resour-
  ceName, the last line in the file is used.

  Any whitespace character before or after the name or colon in a Resour-
  ceSpec are ignored.  To allow a Value to begin with whitespace, the two-
  character sequence ``\_s_p_a_c_e'' (backslash followed by space) is recognized
  and replaced by a space character, and the two-character sequence ``\_t_a_b''
  (backslash followed by horizontal tab) is recognized and replaced by a hor-
  izontal tab character.  To allow a Value to contain embedded newline char-
  acters, 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 ``\_n_e_w_l_i_n_e'' (backslash followed by
  newline) is recognized and removed from the value.  To allow a Value to
  contain arbitrary character codes, the four-character sequence ``\_n_n_n'',
  where each _n is a digit character in the range of ``0''-``7'', is recog-
  nized and replaced with a single byte that contains the octal value speci-
  fied by the sequence.  Finally, the two-character sequence ``\\'' is recog-
  nized and replaced with a single backslash.

  When an application looks for the value of a resource, it specifies a com-
  plete 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 deter-
  mined, and these matching components and bindings are compared according to
  precedence rules.  Each of the rules is applied at each level, before mov-
  ing to the next level, until a rule selects a single entry over all others.
  The rules (in order of precedence) are:

  11..   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).

  22..   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 "?".

  33..   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 follow-
  ing sources (other programs usually support some subset of these sources):

  RREESSOOUURRCCEE__MMAANNAAGGEERR rroooott wwiinnddooww pprrooppeerrttyy
          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 _x_r_d_b program.  This is
          frequently taken care of when the user starts up X through the
          display manager or _x_i_n_i_t.

  SSCCRREEEENN__RREESSOOUURRCCEESS rroooott wwiinnddooww pprrooppeerrttyy
          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
          _x_r_d_b program will sort resources automatically and place them in
          RESOURCE_MANAGER or SCREEN_RESOURCES, as appropriate.

  aapppplliiccaattiioonn--ssppeecciiffiicc ffiilleess
          Directories named by the environment variable XUSERFILESEARCHPATH
          or the environment variable XAPPLRESDIR, plus directories in a
          standard place (usually under /usr/lib/X11/, but this can be over-
          ridden 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 _T_o_o_l_k_i_t _I_n_t_r_i_n_s_i_c_s - _C _L_a_n_g_u_a_g_e _I_n_t_e_r_f_a_c_e manual for
          details.

  XXEENNVVIIRROONNMMEENNTT
          Any user- and machine-specific resources may be specified by set-
          ting 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 $_H_O_M_E/.Xdefaults-_h_o_s_t_n_a_m_e is looked
          for instead, where _h_o_s_t_n_a_m_e is the name of the host where the
          application is executing.

  --xxrrmm _r_e_s_o_u_r_c_e_s_t_r_i_n_g
          Resources can also be specified from the command line.  The
          _r_e_s_o_u_r_c_e_s_t_r_i_n_g 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 --xxrrmm
          arguments may be given on the command line.

  Program resources are organized into groups called _c_l_a_s_s_e_s, so that collec-
  tions of individual resources (each of which are called _i_n_s_t_a_n_c_e_s) 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:

  bbaacckkggrroouunndd ((class BBaacckkggrroouunndd))
          This resource specifies the color to use for the window background.

  bboorrddeerrWWiiddtthh ((class BBoorrddeerrWWiiddtthh))
          This resource specifies the width in pixels of the window border.

  bboorrddeerrCCoolloorr ((class BBoorrddeerrCCoolloorr))
          This resource specifies the color to use for the window border.

  Most applications using the X Toolkit Intrinsics also have the resource
  ffoorreeggrroouunndd (class FFoorreeggrroouunndd), 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:  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

  If these resources were stored in a file called ._X_r_e_s_o_u_r_c_e_s 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 _X_l_i_b manual
  section _R_e_s_o_u_r_c_e _M_a_n_a_g_e_r _F_u_n_c_t_i_o_n_s for more information.




EXAMPLES
  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.

      %  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 $*
      %  xon filesysmachine xload

DIAGNOSTICS
  A wide variety of error messages are generated from various programs.  The
  default error handler in _X_l_i_b (also used by many toolkits) uses standard
  resources to construct diagnostic messages when errors occur.  The defaults
  for these messages are usually stored in /_u_s_r/_l_i_b/_X_1_1/_X_E_r_r_o_r_D_B.  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 set-
  ting the _S_t_r_i_n_g_C_o_n_v_e_r_s_i_o_n_s_W_a_r_n_i_n_g 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 _x_r_d_b program (fre-
  quently called ._X_r_e_s_o_u_r_c_e_s or ._X_r_e_s 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

  XConsortium(1), XStandards(1), Xsecurity(1), appres(1), auto_box(1),
  bdftopcf(1), beach_ball(1), bitmap(1), editres(1), fs(1), fsinfo(1),
  fslsfonts(1), fstobdf(1), ico(1), imake(1), listres(1), lndir(1), mak-
  edepend(1), maze(1), mkdirhier(1), mkfontdir(1), oclock(1), plbpex(1), puz-
  zle(1), resize(1), showfont(1), showrgb(1), twm(1), viewres(1), x11perf(1),
  x11perfcomp(1), xauth(1), xbiff(1), xcalc(1), xclipboard(1), xclock(1),
  xcmsdb(1), xcmstest(1), xconsole(1), xcutsel(1), xditview(1), xdm(1),
  xdpr(1), xdpyinfo(1), xedit(1), xev(1), xeyes(1), xfd(1), xfontsel(1),
  xgas(1), xgc(1), xhost(1), xinit(1), xkill(1), xload(1), xlogo(1), xlsa-
  toms(1), xlsclients(1), xlsfonts(1), xmag(1), xman(1), xmh(1), xmkmf(1),
  xmodmap(1), xon(1), xpr(1), xprop(1), xrdb(1), xrefresh(1), xset(1),
  xsetroot(1), xstdcmap(1), xterm(1), xwd(1), xwininfo(1), xwud(1),
  Xserver(1), Xdec(1), XmacII(1), Xmips(1), Xqdss(1), Xqvss(1), Xsun(1),
  X386(1), kbd_mode(1), _X_l_i_b - _C _L_a_n_g_u_a_g_e _X _I_n_t_e_r_f_a_c_e, and _X _T_o_o_l_k_i_t _I_n_t_r_i_n_-
  _s_i_c_s - _C _L_a_n_g_u_a_g_e _I_n_t_e_r_f_a_c_e

COPYRIGHT

  The following copyright and permission notice outlines the rights and res-
  trictions covering most parts of the core distribution of the X Window Sys-
  tem from MIT.  Other parts have additional or different copyrights and per-
  missions; see the individual source files.

  Copyright 1984, 1985, 1986, 1987, 1988, 1989, 1990, 1991 by the Mas-
  sachusetts Institute of Technology.

  Permission to use, copy, modify, distribute, and sell this software and its
  documentation for any purpose is hereby granted without fee, provided that
  the above copyright notice appear in all copies and that both that copy-
  right notice and this permission notice appear in supporting documentation,
  and that the name of MIT not be used in advertising or publicity pertaining
  to distribution of the software without specific, written prior permission.
  MIT makes no representations about the suitability of this software for any
  purpose.  It is provided "as is" without express or implied warranty.

TRADEMARKS

  X Window System is a trademark of MIT.

AUTHORS

  A cast of thousands, literally.  The MIT Release 5 distribution is brought
  to you by the MIT X Consortium.  The names of all people who made it a
  reality will be found in the individual documents and source files.  The
  staff members at MIT responsible for this release are: Donna Converse (MIT
  X Consortium), Stephen Gildea (MIT X Consortium), Susan Hardy (MIT X Con-
  sortium), Jay Hersh (MIT X Consortium), Keith Packard (MIT X Consortium),
  David Sternlicht (MIT X Consortium), Bob Scheifler (MIT X Consortium), and
  Ralph Swick (Digital/MIT Project Athena).

























