--- /dev/null
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+NAME
+ X - A network transparent window system for Unix
+
+DESCRIPTION
+ X is a network transparent windowing system developed at MIT
+ which runs under Ultrix-32 Version 1.2 and 4.3BSD Unix.
+
+ X display servers run on computers with bitmap terminals.
+ The server distributes user input to, and accepts output
+ requests from various client programs located either on the
+ same machine or elsewhere in the Internet. While a client
+ normally runs on the same machine as the X server it is
+ talking to, this need not be the case.
+
+ X supports overlapping windows, fully recursive subwindows,
+ text and graphics operations within windows. For a full
+ explanation of functions, see ``Xlib - C Language X Inter-
+ face'' document.
+
+ When you first log in on a display running X, you are using
+ the _\bx_\bt_\be_\br_\bm(_\b1) terminal emulator program. You need not learn
+ anything extra to use a display running X as a terminal
+ beyond moving the mouse cursor into the login window to log
+ in normally.
+
+ X attempts to provide hooks for your favorite style of user
+ interface; feel free to write your own if you don't like the
+ style provided by existing window managers (see _\bx_\bw_\bm(_\b1),
+ _\bx_\bn_\bw_\bm(_\b1), or _\bu_\bw_\bm(_\b1)). These programs are used to manipulate
+ existing top level windows, including moving, resizing, and
+ iconifying existing windows. You should start your favorite
+ window manager when you log in on a display running X.
+
+ Current client programs of X include a terminal emulator
+ (_\bx_\bt_\be_\br_\bm(_\b1)), window managers (_\bx_\bw_\bm(_\b1), _\bx_\bn_\bw_\bm(_\b1) and _\bu_\bw_\bm(_\b1)),
+ bitmap editor (_\bb_\bi_\bt_\bm_\ba_\bp(_\b1)), access control program
+ (_\bx_\bh_\bo_\bs_\bt(_\b1)), user preference setting program (_\bx_\bs_\be_\bt(_\b1)), load
+ monitor (_\bx_\bl_\bo_\ba_\bd(_\b1)), clock (_\bx_\bc_\bl_\bo_\bc_\bk(_\b1)), impress previewer
+ (_\bx_\bi_\bm_\bp_\bv(_\b1)), font displayer (_\bx_\bf_\bd(_\b1)), demos (_\bx_\bd_\be_\bm_\bo(_\b1)), and
+ editors (e.g., _\bx_\bt_\be_\bd). On some systems, mail notification
+ has been integrated (_\bb_\bi_\bf_\bf(_\b1)).
+
+OPTIONS
+ The following options can be given on the command line to
+ the X server, usually started by _\bi_\bn_\bi_\bt(_\b1) using information
+ stored in the file /_\be_\bt_\bc/_\bt_\bt_\by_\bs. (see _\bt_\bt_\by_\bs(_\b5), _\bX(_\b8_\bc) for
+ details):
+ -a # sets mouse acceleration (pixels)
+ -c turns off key-click
+ c # sets key-click volume (0-8)
+ -f # sets feep(bell) volume (0-7)
+ -l sets LockUpDownMode
+
+
+
+Printed 9/15/87 25 January 1986 1
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ l sets LockToggleMode
+ m forces "monochrome" mode on a color display
+ -p # sets screen-saver pattern cycle time (minutes)
+ -r turns off auto-repeat
+ r turns on auto-repeat
+ -s # sets screen-saver timeout (minutes)
+ -t # sets mouse threshold (pixels)
+ v sets video-on screen-saver preference
+ -v sets video-off screen-saver preference
+ -0 _\bc_\bo_\bl_\bo_\br sets color map entry 0 (BlackPixel)
+ -1 _\bc_\bo_\bl_\bo_\br sets color map entry 1 (WhitePixel)
+ -D _\br_\bg_\bb_\bd_\bb sets RGB database file
+
+ The defaults are ``-a 4 c 6 -f 3 l -p 60 r -s 10 -t 2 -0
+ #008 -1 #ffffff -D /usr/lib/rgb''.
+
+
+
+X DEFAULTS
+ Many X programs follow the convention of using a file called
+ ._\bX_\bd_\be_\bf_\ba_\bu_\bl_\bt_\bs in your home directory to allow tailoring the
+ default values of many items on the display (default font,
+ border width, icon behavior, and so on). The format of this
+ file is ``programname.keyword:value'', where the default
+ value for each keyword is set to the specified string. If
+ the program name is missing, the default ``keyword'' value
+ is set to the value for all programs. Case is not signifi-
+ cant in keywords. Any whitespace before the value is
+ ignored. Any global defaults should precede program
+ defaults in the file. See the manual pages for a list of
+ what defaults can be set in a given program. Here is an
+ overblown example ~/._\bX_\bd_\be_\bf_\ba_\bu_\bl_\bt_\bs file.
+
+ # this is a comment
+ .BorderWidth: 2
+ .BitmapIcon: on
+ .MakeWindow.Background:#8e8
+ .MakeWindow.Border: #f26
+ .MakeWindow.BodyFont:cor
+ .MakeWindow.Foreground:medium slate blue
+ .MakeWindow.Freeze: on
+ .MakeWindow.Mouse: #e6f
+ .MakeWindow.MouseMask:black
+ .MakeWindow.ClipToScreen:on
+ .Menufreeze: on
+ .Menubackground: maroon
+ .Panefont: 8x13
+ .SelectionFont: 8x13
+ .SelectionBorder: black
+ .Paneborderwidth: 1
+ xterm.Panespread: .25
+ biff.Background: violet red
+
+
+
+Printed 9/15/87 25 January 1986 2
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ biff.BodyFont: 9x15
+ biff.Border: black
+ biff.Foreground: green yellow
+ biff.Mouse: coral
+ bitmap.Background: forest green
+ bitmap.Border: salmon
+ bitmap.Foreground: white
+ bitmap.Highlight: red
+ bitmap.Mouse: black
+ xclock.Background: plum
+ xclock.Border: black
+ xclock.Foreground: red
+ xclock.Highlight: blue
+ xclock.Mode: analog
+ xshell.action.LeftButton:xterm =80x65-0+0 -fn 6x10
+ xshell.action.MiddleButton:xted =80x65+0-0
+ xshell.action.RightButton:xterm =20x20-0-0 -fn 6x10 -e dc
+ xshell.action.$: xterm =80x65+0+0 -fn 6x10 -e sh
+ xshell.action.#: xterm =80x65+0+0 -fn 6x10 -e su
+ xshell.ReverseVideo:on
+ xshell.WindowGeometry:=-0-0
+ xshell.Quiet: on
+ xdemo.Background: white
+ xdemo.Border: black
+ xdemo.balls.Background:maroon
+ xdemo.balls.Foreground:white
+ xdemo.circles.Foreground:khaki
+ xdemo.draw.Background:light gray
+ xdemo.draw.BodyFont:oldeng
+ xdemo.draw.Foreground:midnight blue
+ xdemo.draw.Mouse: white
+ xdemo.menulife.Background:medium turquoise
+ xdemo.menulife.Foreground:orange red
+ xdemo.menulife.MenuBackground:light blue
+ xdemo.menulife.MenuFont:oldeng
+ xdemo.menulife.MenuForeground:dark orchid
+ xdemo.menulife.MenuMouse:orange
+ xdemo.menulife.Mouse:salmon
+ xdemo.plaid.Foreground:red
+ xdemo.qix.Foreground:violet red
+ xdemo.slide.Foreground:forest green
+ xdemo.wallpaper.Foreground:medium turquoise
+ xdemo.xor.Foreground:blue violet
+ ximpv.Background: dark green
+ ximpv.Border: red
+ ximpv.Foreground: cyan
+ ximpv.Mouse: white
+ xload.Background: #ff0068
+ xload.Border: black
+ xload.Foreground: slate blue
+ xload.Highlight: yellow
+ xload.ReverseVideo: on
+
+
+
+Printed 9/15/87 25 January 1986 3
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ xted.Background: firebrick
+ xted.BodyFont: kiltercrn
+ xted.Border: tan
+ xted.Cursor: yellow
+ xted.Foreground: white
+ xted.Highlight: goldenrod
+ xted.Mouse: cyan
+ xterm.Background: #355
+ xterm.BodyFont: 6x13p
+ xterm.Cursor: green
+ xterm.Foreground: white
+ xfax.Background: white
+ xfax.Border: green
+ xfax.Foreground: red
+ xfax.Mouse: blue
+
+ By default when you log in, only programs running on your
+ local computer will be allowed to interact with your
+ display. If someone else on a different machine wants to
+ show you something, you can use the _\bx_\bh_\bo_\bs_\bt(_\b1) program to
+ allow access to your display.
+
+SIZING WINDOWS
+ Many programs ask you to manually size their top-level win-
+ dow. When started, such a program will typically popup an
+ identification window in the upper left corner of the
+ display. The window can be created with the center button:
+ press the button to define one corner of the window, move
+ the cursor to where the opposite corner of the window should
+ be and release the button. For text applications, the left
+ and right buttons can also be used. Pressing the left but-
+ ton typically produces an 80 by 24 window, which can then be
+ moved around, and placed by releasing the button. Simi-
+ larly, the right button typically produces an 80 by full
+ screen window. For graphics applications, the left button
+ typically creates a default size window in a default loca-
+ tion, while the right button creates a default size window
+ at the position of the cursor.
+
+ Most applications (e.g., _\bx_\bt_\be_\bd, _\bx_\bd_\be_\bm_\bo, and _\bx_\bf_\ba_\bx) read options
+ to control sizing of initial windows. The
+ ``MakeWindow.BodyFont'' option controls the font for the
+ popup window. The ``MakeWindow.BorderWidth'' and
+ ``MakeWindow.InternalBorder'' options control the outer and
+ inner borders. The ``MakeWindow.ReverseVideo'' option can be
+ set to ``on'' to reverse colors. On color displays, the
+ ``MakeWindow.Foreground'', ``MakeWindow.Background'', and
+ ``MakeWindow.Border'' options control the color of the popup
+ window, and the ``MakeWindow.Mouse'' and
+ ``MakeWindow.MouseMask'' options control the color of the
+ mouse cursor. The ``MakeWindow.Freeze'' option, when set to
+ ``on'', will stop all other output while the window is
+
+
+
+Printed 9/15/87 25 January 1986 4
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ sized, and use a steady outline instead of continuously
+ flashing the window outline. The
+ ``MakeWindow.ClipToScreen'' option will clip the resulting
+ window to fit on the screen. (Currently only implemented in
+ programs using the _\bX_\bC_\br_\be_\ba_\bt_\be_\bT_\be_\br_\bm subroutine.)
+
+GEOMETRY SPECIFICATION
+ Most programs accept a geometry specification. This allows
+ automatic creation and placement of windows on the screen at
+ login and other convenient times.
+ =[WIDTH][xHEIGHT][{+-}XOFF[{+-}YOFF]] The []'s denote
+ optional parameters, the {}'s surround alternatives. WIDTH
+ and HEIGHT are in number of characters for text oriented
+ applications, and usually in pixels for graphics oriented
+ applications. XOFF and YOFF are in pixels. If you don't
+ give XOFF and/or YOFF, then you must use the mouse to create
+ the window. If you give XOFF and/or YOFF, then a WIDTHx-
+ HEIGHT window will automatically be creating without inter-
+ vention. XOFF and YOFF specify deltas from a corner of the
+ screen to the corresponding corner of the window, as fol-
+ lows:
+ +XOFF+YOFF upper left to upper left
+ -XOFF+YOFF upper right to upper right
+ +XOFF-YOFF lower left to lower left
+ -XOFF-YOFF lower right to lower right
+
+KEYBOARD
+ If you don't like the standard keyboard layout or the
+ default definitions of keymap and function keys, the key-
+ boards on most displays can be remapped to suit your taste.
+ Many programs look for a file called ._\bX_\bk_\be_\by_\bm_\ba_\bp in your home
+ directory. This is a binary file, produced from a source
+ map with the _\bk_\be_\by_\bc_\bo_\bm_\bp(_\b1) program.
+
+COLORS
+ Many programs allow you to specify colors for background,
+ border, text, etc. A color specification can be given
+ either as an english name (see /_\bu_\bs_\br/_\bl_\bi_\bb/_\br_\bg_\bb._\bt_\bx_\bt for defined
+ names), or three hexadecimal values for the red, green, and
+ blue components, in one of the following formats:
+
+ #RGB
+ #RRGGBB
+ #RRRGGGBBB
+ #RRRRGGGGBBBB
+
+DISPLAY SPECIFICATION
+ When you first log in, the environment variable ``DISPLAY''
+ will be set to a string ``machine:display'' (for example,
+ ``mit-athena:0'') which will determine which display an X
+ application will talk to by default.
+
+
+
+
+Printed 9/15/87 25 January 1986 5
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ Most applications will also interpret an argument with a
+ ``:'' in it to be the display to use.
+
+ When using DECnet, the format ``node::display'' should be
+ used.
+
+MENU DEFAULTS
+ As there is now a standard menu package for X (_\bX_\bM_\be_\bn_\bu(_\b3_\bx)),
+ you can tune the behavior of menus in programs using this
+ package with a set of _\bX_\bd_\be_\bf_\ba_\bu_\bl_\bt_\bs. _\bX_\bt_\be_\br_\bm's `Mode Menu' is
+ controlled by these defaults for example.
+
+ MenuFreeze
+ Determines whether or not to grab the _\bX server while
+ a menu is posted. One of: on, off. The default
+ value is off.
+
+ MenuStyle
+ Determines the menu display style. One of:
+ left_hand, right_hand, center. The default value is
+ right_hand.
+
+ MenuMode
+ Determines the menu selection high light mode. One
+ of: box, invert. If box mode is chosen then the
+ SelectionBorderWidth and SelectionBorderColor param-
+ eters effect the box line width and color respec-
+ tively. If invert mode is chose then the Selection-
+ Foreground and MenuBackground colors are used for
+ the inversion. The default value is invert.
+
+ MenuMouse
+ Determines the color of the mouse cursor while it is
+ within the menu. Any valid _\bX color may be used.
+ The default value is black.
+
+ MenuBackground
+ Determines the menu background color. Any valid _\bX
+ color may be used. The default value is white.
+
+ MenuInactivePattern
+ Determines which of the five possible bitmap pat-
+ terns will be used to tile inactive panes. One of:
+ dimple1, dimple3, gray1, gray3, cross_weave. The
+ default value is gray3.
+
+ PaneStyle
+ Determines the display style of all menu panes. One
+ of: flush_left, flush_right, center. The default
+ value is center.
+
+
+
+
+
+Printed 9/15/87 25 January 1986 6
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ PaneFont
+ Determines the font used for the label (heading
+ text) of each pane. Any valid _\bX font may be used.
+ The default value is 8x13.
+
+ PaneForeground
+ Determines the pane foreground color. This is the
+ color used for the label (heading text) in each
+ pane. Any valid _\bX color may be used. The default
+ value is black.
+
+ PaneBorder
+ Determines the color of all menu pane borders. Any
+ valid _\bX color may be used. The default value is
+ black.
+
+ PaneBorderWidth
+ Determines the width (in pixels) of all menu pane
+ borders. Any integer greater than or equal to 0 may
+ be used. The default value is 2.
+
+ PaneSpread
+ Determines the horizontal spread of menu panes. Any
+ double greater than or equal to 0.0 may be used. A
+ value of 1.0 specifies a one to one ratio between
+ horizontal spread and vertical spread. A value less
+ than 1.0 will compress the menu panes inward and a
+ value greater than 1.0 will expand them outward.
+ The default value is 1.0.
+
+ SelectionStyle
+ Determines the display style of all menu selections.
+ One of: flush_left, flush_right, center. The
+ default value is flush_left.
+
+ SelectionFont
+ Determines the font used for the text in each selec-
+ tion. Any valid X font may be used. The default
+ value is 6x10.
+
+ SelectionForeground
+ Determines the selection foreground color. This is
+ the color used for the text in each selection. Any
+ valid _\bX color may be used. The default value is
+ black.
+
+ SelectionBorder
+ Determines the color of all menu selection borders.
+ Any valid _\bX color may be used. The default value is
+ black.
+
+
+
+
+
+Printed 9/15/87 25 January 1986 7
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ SelectionBorderWidth
+ Determines the width (in pixels) of all menu selec-
+ tion borders. Any integer greater than or equal to
+ 0 may be used. The default value is 1.
+
+ SelectionSpread
+ Determines the inter-selection spread. Any double
+ greater than or equal to 0.0 may be used. A value
+ of 1.0 specifies that 1.0 times the height of the
+ current selection font will be used for padding The
+ default value is 0.25.
+
+SEE ALSO
+ X(8c), xterm(1), bitmap(1), xwm(1), xnwm(1), xhost(1),
+ xclock(1), xload(1), xset(1), keycomp(1), xdemo(1), biff(1),
+ qv(4), vs(4), init(8), ttys(5), uwm(1), xrefresh(1),
+ xwininfo(1), ximpv(1), xdvi(1), pikapix(1), xwd(1), xwud(1),
+ xinit(1), xted(1), xdemo(1), Xqvss(8c), Xvs100(8c),
+ Xsun(8c), Xnest(8c)
+ `Xlib - C Language X Interface'
+
+AUTHORS
+ It is no longer feasible to list all people who have contri-
+ buted something to X; below is a short list of people who
+ have added significant code to device independent parts of
+ X.
+ Bob Scheifler (MIT-LCS), Jim Gettys (MIT-Project Athena,
+ DEC), Mark Vandevoorde (MIT-Project Athena, DEC), Tony Della
+ Fera (MIT-Project Athena, DEC), Ron Newman (MIT-Project
+ Athena, MIT), Shane Hartman and Stuart Malone (MIT-LCS),
+ Doug Mink (Smithsonian Astrophysical Observatory), Bob
+ McNamara (DEC-MAD), and Stephen Sutphen (University of
+ Alberta).
+
+ Special thanks must go to Paul Asente (of DECWRL and Stan-
+ ford University), who wrote "W" which saved us much time and
+ energy early in this project, and who is now an active X
+ contributor as well, and Chris Kent (of DECWRL and Purdue
+ University) who both struggled mightily (and won!) to turn
+ the Vs100 into something useful under Unix.
+
+ We are very grateful for the interest shown by many groups
+ in the country, which has encouraged us to make X more than
+ our personal toy. Great thanks must go to Digital's Ultrix
+ Engineering Group for the QDSS implementation, and to
+ Digital's Workstations Group for the QVSS implementation.
+
+
+ Copyright (c) 1984, 1985, 1986 by Massachusetts Institute of
+ Technology.
+
+ Permission to use, copy, modify, and distribute this
+
+
+
+Printed 9/15/87 25 January 1986 8
+
+
+
+
+
+
+X(1) UNIX Programmer's Manual X(1)
+
+
+
+ software and its documentation for any purpose and without
+ fee is hereby granted, provided that the above copyright
+ notice appear in all copies and that both that copyright
+ notice and this permission notice appear in supporting docu-
+ mentation, and that the name of M.I.T. not be used in
+ advertising or publicity pertaining to distribution of the
+ software without specific, written prior permission. M.I.T.
+ makes no representations about the suitability of this
+ software for any purpose. It is provided "as is" without
+ express or implied warranty.
+
+ This software is not subject to any license of the American
+ Telephone and Telegraph Company or of the Regents of the
+ University of California.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 25 January 1986 9
+
+
+
--- /dev/null
+
+
+
+BIFF(1) UNIX Programmer's Manual BIFF(1)
+
+
+
+NAME
+ biff - be notified if mail arrives and who it is from
+
+SYNOPSIS
+ biff [ yn ]
+
+DESCRIPTION
+ _\bB_\bi_\bf_\bf informs the system whether you want to be notified when
+ mail arrives during the current terminal session. The com-
+ mand
+
+ biff y
+
+ enables notification; the command
+
+ biff n
+
+ disables it. When mail notification is enabled, the header
+ and first few lines of the message will be printed on your
+ screen whenever mail arrives. A ``biff y'' command is often
+ included in the file ._\bl_\bo_\bg_\bi_\bn or ._\bp_\br_\bo_\bf_\bi_\bl_\be to be executed at
+ each login.
+
+ _\bB_\bi_\bf_\bf operates asynchronously. For synchronous notification
+ use the MAIL variable of _\bs_\bh(1) or the _\bm_\ba_\bi_\bl variable of
+ _\bc_\bs_\bh(1).
+
+X WINDOW SYSTEM
+ If you are logged in under the X window system, a popup win-
+ dow is used instead of a message to your login window. To
+ delete the window, click any mouse button with the mouse in
+ the window. Properties of the window can be controlled with
+ options for _\bb_\bi_\bf_\bf in your ._\bX_\bd_\be_\bf_\ba_\bu_\bl_\bt_\bs file. The following
+ options are recognized:
+
+ Background
+ To determine the background color.
+
+ Border To determine the border color.
+
+ BorderWidth
+ To determine the border width. Default is 2.
+
+ BodyFont
+ To determine text font. Default is 8x13.
+
+ Foreground
+ To determine the foreground color.
+
+ InternalBorder
+ To determine the padding around the text. Default
+ is 2.
+
+
+
+Printed 9/15/87 4 September 1985 1
+
+
+
+
+
+
+BIFF(1) UNIX Programmer's Manual BIFF(1)
+
+
+
+ Mouse To determine the mouse cursor color.
+
+ Offset To determine the vertical position of the window.
+ Positive is offset from the top of the screen, nega-
+ tive is from the bottom. Default is 2. Window is
+ centered horizontally.
+
+ ReverseVideo
+ If ``on'', the window should be white on black
+ instead of black on white. Default is off.
+
+ Timeout In the event you don't click in the window, speci-
+ fies the maximum number of minutes the window should
+ remain on the screen. Value of zero means infinite.
+ Default is zero.
+
+ Volume Controls the volume of the bell. Default is zero.
+
+SEE ALSO
+ csh(1), sh(1), mail(1), X(1), comsat(8C)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 4 September 1985 2
+
+
+
--- /dev/null
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+NAME
+ bitmap - bitmap editor for X window system
+
+
+SYNOPSIS
+ bitmap filename [_\bd_\bi_\bm_\be_\bn_\bs_\bi_\bo_\bn_\bs] [_\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by] [=_\bg_\be_\bo_\bm_\be_\bt_\br_\by]
+
+
+DESCRIPTION
+ _\bb_\bi_\bt_\bm_\ba_\bp lets you interactively create small bitmaps, or edit
+ previously created bitmaps. A bitmap is a small picture,
+ represented as a rectangular array of 0 and 1 bits. The X
+ window system uses bitmaps to represent cursors and icons,
+ among other things.
+
+ When you run _\bb_\bi_\bt_\bm_\ba_\bp, you are given a magnified version of
+ the bitmap, with each pixel blown up into a large square,
+ like a piece of graph paper. You can then use the mouse to
+ set, clear, or invert individual pixels, and can invoke com-
+ mands to set, clear or invert larger rectangular areas of
+ the bitmap. Other commands allow you to move or copy rec-
+ tangular areas from one part of the bitmap to another, and
+ to define a `hot spot'--a special single point on the bit-
+ map, which is useful when the bitmap is used as an X cursor.
+
+ The output of the _\bb_\bi_\bt_\bm_\ba_\bp program is a small program frag-
+ ment. By #include'ing such a program fragment in your C
+ program, you can easily declare the size and contents of
+ cursors, icons, and other bitmaps that your program creates
+ to deal with the X window system.
+
+ When _\bb_\bi_\bt_\bm_\ba_\bp starts, it first tries to read the specified
+ file (see FILE FORMAT). If the file already exists, it
+ creates a window containing a grid of the appropriate dimen-
+ sions.
+
+ If the file does not exist, _\bb_\bi_\bt_\bm_\ba_\bp will create a window for
+ a bitmap of the size specified by _\bd_\bi_\bm_\be_\bn_\bs_\bi_\bo_\bn_\bs , which should
+ be two numbers separated by the letter `x' (e.g. 7x9,
+ 13x21). The first number is the bitmap's width; the second
+ is its height. The bitmap will start out empty. If no
+ dimensions are specified on the command line, a 16x16 bitmap
+ will be created. The absolute limit is 99x99; the practical
+ limit is somewhat lower, and depends on the size and resolu-
+ tion of your display.
+
+ _\bb_\bi_\bt_\bm_\ba_\bp accepts two other optional command line arguments.
+ You may specify a display name in the form _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by (see
+ _\bX(_\b1)). And you may provide a geometry specification. If
+ you don't give a geometry specification, _\bb_\bi_\bt_\bm_\ba_\bp will ask you
+ where you want to put the window when it starts up. See
+ _\bX(_\b1) for a full explanation.
+
+
+
+Printed 9/15/87 29 January 1986 1
+
+
+
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+ The window that _\bb_\bi_\bt_\bm_\ba_\bp creates has four parts. The largest
+ section is the checkerboard grid, which is a magnified ver-
+ sion of the bitmap you are editing. At the upper left is a
+ set of commands that you can invoke with any mouse button.
+ Below the commands is an "actual size" picture of the bitmap
+ you are editing; below that is an inverted version of the
+ same bitmap. Each time you change the grid, the same change
+ will occur in the actual-size bitmap and its inverse.
+
+ If you use a window manager to make the _\bb_\bi_\bt_\bm_\ba_\bp window larger
+ or smaller, the grid squares will automatically get larger
+ or smaller as well.
+
+
+COMMANDS
+ (Note for users of color displays: In all of the following,
+ ``white'' means the background color, and ``black'' means
+ the foreground color. You may specify a foreground and
+ background color in your ._\bX_\bd_\be_\bf_\ba_\bu_\bl_\bt_\bs file; see the X
+ DEFAULTS section below.)
+
+ When the cursor is in the checkerboard region, each mouse
+ button has a different effect upon the single square that
+ the cursor is over.
+
+ The _\bl_\be_\bf_\bt _\bm_\bo_\bu_\bs_\be _\bb_\bu_\bt_\bt_\bo_\bn turns a grid square black and sets the
+ corresponding bitmap bit to 1.
+
+ The _\br_\bi_\bg_\bh_\bt _\bm_\bo_\bu_\bs_\be _\bb_\bu_\bt_\bt_\bo_\bn turns a grid square white and sets
+ the corresponding bitmap bit to 0.
+
+ The _\bm_\bi_\bd_\bd_\bl_\be _\bm_\bo_\bu_\bs_\be _\bb_\bu_\bt_\bt_\bo_\bn inverts a grid square, turning it
+ white if it was black, or black if it was white. It also
+ inverts the corresponding bitmap bit, setting it to 0 if it
+ was 1, and to 1 if it was 0.
+
+ You can also invoke more sophisticated commands by moving
+ the mouse over one of the command boxes at the upper right
+ corner, and pressing any mouse button.
+
+
+ _\bC_\bl_\be_\ba_\br _\bA_\bl_\bl
+ turns all the grid squares white and sets all bitmap
+ bits to 0. This is irreversible, so invoke it with
+ care.
+
+
+ _\bS_\be_\bt _\bA_\bl_\bl turns all the grid squares black and sets all bitmap
+ bits to 1. This is also irreversible.
+
+
+
+
+
+
+Printed 9/15/87 29 January 1986 2
+
+
+
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+ _\bI_\bn_\bv_\be_\br_\bt _\bA_\bl_\bl
+ inverts all the grid squares and bitmap bits, as if
+ you had pressed the middle mouse button over each
+ square.
+
+
+ _\bC_\bl_\be_\ba_\br _\bA_\br_\be_\ba
+ clears a rectangular area of the grid, turning it
+ white and setting the corresponding bitmap bits to
+ 0. After you click over this command, the cursor
+ turns into an `upper-left corner'. Press any mouse
+ button over the upper-left corner of the area you
+ want to invert, and _\bh_\bo_\bl_\bd _\bt_\bh_\be _\bb_\bu_\bt_\bt_\bo_\bn _\bd_\bo_\bw_\bn while mov-
+ ing the mouse to the lower-right corner of the area
+ you want to invert, then let the button up.
+
+ While you are holding down the button, the selected
+ area will be covered with X's, and the cursor will
+ change to a `lower-right corner'. If you now wish
+ to abort the command without clearing an area,
+ either press another mouse button, move the cursor
+ outside the grid, or move the cursor to the left of
+ or above the upper-left corner.
+
+
+ _\bS_\be_\bt _\bA_\br_\be_\ba
+ turns a rectangular area of the grid black and sets
+ the corresponding bitmap bits to 1. It works the
+ same way as the _\bC_\bl_\be_\ba_\br _\bA_\br_\be_\ba command.
+
+
+ _\bI_\bn_\bv_\be_\br_\bt _\bA_\br_\be_\ba
+ inverts a rectangular area of the grid. It works
+ the same way as the _\bC_\bl_\be_\ba_\br _\bA_\br_\be_\ba command.
+
+
+ _\bC_\bo_\bp_\by _\bA_\br_\be_\ba
+ copies a rectangular area from one part of the grid
+ to another. First, you select the rectangle to be
+ copied, in the manner described under _\bC_\bl_\be_\ba_\br _\bA_\br_\be_\ba
+ above. Then, the cursor will change to an "upper-
+ left corner". When you press a mouse button, a des-
+ tination rectangle will overlay the grid; moving
+ the mouse while holding down the button will move
+ this destination rectangle. The copy will occur
+ when you let up the button. To cancel the copy,
+ move the mouse outside the grid and then let up the
+ button.
+
+ _\bM_\bo_\bv_\be _\bA_\br_\be_\ba
+ works identically to _\bC_\bo_\bp_\by _\bA_\br_\be_\ba, _\be_\bx_\bc_\be_\bp_\bt that it
+ clears the source rectangle after copying to the
+
+
+
+Printed 9/15/87 29 January 1986 3
+
+
+
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+ destination.
+
+
+ _\bL_\bi_\bn_\be will draw a line between two points.
+
+
+ _\bC_\bi_\br_\bc_\bl_\be will draw a circle specifying the center and a
+ radius
+
+
+ _\bF_\bi_\bl_\bl_\be_\bd _\bC_\bi_\br_\bc_\bl_\be
+ will draw a filled circle given the center and
+ radius of the circle.
+
+ _\bS_\be_\bt _\bH_\bo_\bt_\bs_\bp_\bo_\bt
+ designates a point on the bitmap as the "hot spot".
+ If a program is using your bitmap as a cursor, the
+ hot spot indicates which point on the bitmap is the
+ "actual" location of the cursor. For instance, if
+ your cursor is an arrow, the hot spot should be the
+ tip of the arrow; if your cursor is a cross, the
+ hot spot should be where the perpendicular lines
+ intersect.
+
+
+ _\bC_\bl_\be_\ba_\br _\bH_\bo_\bt_\bs_\bp_\bo_\bt
+ removes any hot spot that was defined on this bit-
+ map.
+
+
+ _\bW_\br_\bi_\bt_\be _\bO_\bu_\bt_\bp_\bu_\bt
+ writes the current bitmap value to the file speci-
+ fied in the original command line. If the file
+ already exists, the original file is first renamed
+ to filename~ (in the manner of _\be_\bm_\ba_\bc_\bs(_\b1) and other
+ text editors).
+
+ If either the renaming or the writing cause an error
+ (e.g. ``Permission denied'), a Macintosh-style dia-
+ log window will appear, asking if you want to write
+ the file /_\bt_\bm_\bp/_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be instead. If you say yes, all
+ future ``Write Output'' commands will write to
+ /_\bt_\bm_\bp/_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be as well. See below for the format of
+ the output file.
+
+
+ _\bQ_\bu_\bi_\bt exits the _\bb_\bi_\bt_\bm_\ba_\bp program. If you have edited the
+ bitmap and have not invoked _\bW_\br_\bi_\bt_\be _\bO_\bu_\bt_\bp_\bu_\bt, or you
+ have edited it since the last time you invoked _\bW_\br_\bi_\bt_\be
+ _\bO_\bu_\bt_\bp_\bu_\bt, a Macintosh-style dialog window will appear,
+ asking if you want to save changes before quitting.
+ ``Yes'' does a ``Write Output'' before exiting;
+
+
+
+Printed 9/15/87 29 January 1986 4
+
+
+
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+ ``No'' just exits, losing the edits; ``Cancel''
+ means you decided not to quit after all.
+
+
+
+FILE FORMAT
+ _\bB_\bi_\bt_\bm_\ba_\bp reads and writes files in the following format, which
+ is suitable for #include'ing in a C program:
+ #define foo_width 9
+ #define foo_height 13
+ #define foo_x_hot 4
+ #define foo_y_hot 6
+ static short foo_bits[] = {
+ 0x0010, 0x0038, 0x007c, 0x0010,
+ 0x0010, 0x0010, 0x01ff, 0x0010,
+ 0x0010, 0x0010, 0x007c, 0x0038,
+ 0x0010};
+
+ The variables ending with __\bx__\bh_\bo_\bt and __\by__\bh_\bo_\bt are optional;
+ they will be present only if a hot spot has been defined for
+ this bitmap. The other variables must be present.
+
+ In place of ``foo'', the five variables will be prefixed
+ with a string derived from the name of the file that you
+ specified on the original command line by
+ (1) deleting the directory path (all characters up to and
+ including the last `/', if one is present)
+ (2) deleting the extension (the first `.', if one is
+ present, and all characters beyond it)
+
+ For example, invoking _\bb_\bi_\bt_\bm_\ba_\bp with filename
+ /_\bu_\bs_\br/_\bi_\bn_\bc_\bl_\bu_\bd_\be/_\bb_\bi_\bt_\bm_\ba_\bp_\bs/_\bc_\br_\bo_\bs_\bs._\bb_\bi_\bt_\bm_\ba_\bp will produce a file with
+ variable names _\bc_\br_\bo_\bs_\bs__\bw_\bi_\bd_\bt_\bh, _\bc_\br_\bo_\bs_\bs__\bh_\be_\bi_\bg_\bh_\bt, and _\bc_\br_\bo_\bs_\bs__\bb_\bi_\bt_\bs
+ (and _\bc_\br_\bo_\bs_\bs__\bx__\bh_\bo_\bt and _\bc_\br_\bo_\bs_\bs__\by__\bh_\bo_\bt if a hot spot is defined).
+
+ It's easy to define a bitmap or cursor in an X program by
+ simply #include'ing a bitmap file and referring to its vari-
+ ables. For instance, to use a cursor defined in the files
+ _\bt_\bh_\bi_\bs._\bc_\bu_\br_\bs_\bo_\br and _\bt_\bh_\bi_\bs__\bm_\ba_\bs_\bk._\bc_\bu_\br_\bs_\bo_\br, one simply writes
+
+ #include "this.cursor"
+ #include "this_mask.cursor"
+ XCreateCursor (this_width, this_height, this_bits, this_mask_bits,
+ this_x_hot, this_y_hot, foreground, background, func);
+
+ where _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd and _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd are color values, and _\bf_\bu_\bn_\bc
+ is a display function (normally GXcopy).
+
+ An X program can also read a bitmap file at runtime by using
+ the function _\bX_\bR_\be_\ba_\bd_\bB_\bi_\bt_\bm_\ba_\bp_\bF_\bi_\bl_\be.
+
+
+
+
+
+Printed 9/15/87 29 January 1986 5
+
+
+
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+X DEFAULTS
+ Background
+ The window's background color. Bits which are 0 in
+ the bitmap are displayed in this color. This option
+ is useful only on color displays. Default: white.
+
+ Border The border color. This option is useful only on
+ color displays. Default: black.
+
+ BorderWidth
+ The border width. Default: 3.
+
+ BodyFont
+ The text font. Default: vtsingle.
+
+ Foreground
+ The foreground color. Bits which are 1 in the bit-
+ map are displayed in this color. This option is
+ useful only on color displays. Default: black.
+
+ Highlight
+ The highlight color. _\bb_\bi_\bt_\bm_\ba_\bp uses this color to show
+ the hot spot and to indicate rectangular areas that
+ will be affected by the _\bM_\bo_\bv_\be _\bA_\br_\be_\ba, _\bC_\bo_\bp_\by _\bA_\br_\be_\ba, _\bS_\be_\bt
+ _\bA_\br_\be_\ba, and _\bI_\bn_\bv_\be_\br_\bt _\bA_\br_\be_\ba commands. If a highlight
+ color is not given, then _\bb_\bi_\bt_\bm_\ba_\bp will highlight by
+ inverting. This option is useful only on color
+ displays.
+
+
+ Mouse The mouse cursor's color. This option is useful
+ only on color displays. Default: black.
+
+
+ENVIRONMENT
+ DISPLAY - the default host and display number.
+
+
+SEE ALSO
+ X(1), Xlib Documentation.
+
+
+
+DIAGNOSTICS
+ The following messages may be displayed in the C-shell that
+ you invoked _\bb_\bi_\bt_\bm_\ba_\bp with. Any of these conditions aborts
+ _\bb_\bi_\bt_\bm_\ba_\bp before it can create its window.
+
+
+ ``bitmap: could not connect to X server on _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by''
+
+ Either the display given on the command line or the DISPLAY
+
+
+
+Printed 9/15/87 29 January 1986 6
+
+
+
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+ environment variable has an invalid host name or display
+ number, or the host is down, or the host is unreachable, or
+ the host is not running an X server, or the host is refusing
+ connections.
+
+ ``bitmap: no file name specified''
+
+ You invoked _\bb_\bi_\bt_\bm_\ba_\bp with no command line arguments. You must
+ give a file name as the first argument.
+
+
+ ``bitmap: could not open file _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be for reading -- _\bm_\be_\bs_\b-
+ _\bs_\ba_\bg_\be''
+
+ The specified file exists but cannot be read, for the reason
+ given in <message> (e.g., permission denied).
+
+
+ ``bitmap: invalid dimensions _\bs_\bt_\br_\bi_\bn_\bg''
+ ``bitmap: dimensions must be positive''
+
+ The second command line argument was not a valid dimension
+ specification.
+
+
+ ``bitmap: file _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be does not have a valid width dimen-
+ sion''
+ ``bitmap: file _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be does not have a valid height
+ dimension''
+ ``bitmap: file _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be has an invalid _\bnth array element''
+
+ The input file is not in the correct format; the program
+ gave up when trying to read the specified data.
+
+
+ The following messages may be displayed in the C-shell after
+ _\bb_\bi_\bt_\bm_\ba_\bp creates its window:
+
+ ``bitmap: Unrecognized variable _\bn_\ba_\bm_\be in file _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be''
+
+ _\bb_\bi_\bt_\bm_\ba_\bp encountered a variable ending in something other than
+ __\bx__\bh_\bo_\bt, __\by__\bh_\bo_\bt, __\bw_\bi_\bd_\bt_\bh, or __\bh_\be_\bi_\bg_\bh_\bt while parsing the input
+ file. It will ignore this variable and continue parsing the
+ file.
+
+
+ ``bitmap: XError: _\bm_\be_\bs_\bs_\ba_\bg_\be''
+ ``bitmap: XIOError''
+
+ A protocol error occurred. Something is wrong with either
+ the X server or the X library which the program was compiled
+ with. Possibly they are incompatible. If the server is not
+
+
+
+Printed 9/15/87 29 January 1986 7
+
+
+
+
+
+
+BITMAP(1) UNIX Programmer's Manual BITMAP(1)
+
+
+
+ on the local host, maybe the connection broke.
+
+
+
+BUGS
+ Doesn't take enough command line options yet. Most
+ options can be specified only through ._\bX_\bd_\be_\bf_\ba_\bu_\bl_\bt_\bs.
+
+ If you move the mouse too fast while holding a mouse but-
+ ton down, some squares may be `missed'. This is caused by
+ limitations in how frequently the X server can sample the
+ mouse location.
+
+ There is no way to write to a file other than that speci-
+ fied on the command line.
+
+ There is no way to change the size of the bitmap once the
+ program is started.
+
+ Edits are unrecoverably lost if you terminate the program
+ with a ^C or ^ in the shell which invoked it, or if you kill
+ it with the shell's ``kill'' command.
+
+ Dimensions greater than 99 are not read properly from the
+ command line or input file. Generally such dimensions would
+ not be useful anyway, since they would produce a window
+ larger than most displays.
+
+
+AUTHOR
+ Copyright (c) 1986 by Massachusetts Institute of Technology.
+ Ron Newman, MIT Project Athena
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 29 January 1986 8
+
+
+
--- /dev/null
+
+
+
+KEYCOMP(1) UNIX Programmer's Manual KEYCOMP(1)
+
+
+
+NAME
+ keycomp - X window system keyboard mapping file compiler
+
+SYNOPSIS
+ keycomp < input_file > output_file
+
+DESCRIPTION
+ Programs that use the X window system, such as _\bx_\bt_\be_\br_\bm(_\b1),
+ need some way to translate the user's key strokes into char-
+ acter strings. Such programs look up this keyboard-to-
+ character string mapping in a binary keymap file by calling
+ the library routine _\bX_\bL_\bo_\bo_\bk_\bu_\bp_\bM_\ba_\bp_\bp_\bi_\bn_\bg. Initially, this routine
+ looks for the file ._\bX_\bk_\be_\by_\bm_\ba_\bp in the user's home directory; if
+ this file doesn't exist, uses a built in table.
+
+ The compiled file format produced by _\bk_\be_\by_\bc_\bo_\bm_\bp should be port-
+ able across machine architectures.
+
+ The _\bk_\be_\by_\bc_\bo_\bm_\bp program (an abbreviation for ``keymap com-
+ piler'') reads in a textual description of this mapping and
+ produces a binary keymap file on its standard output.
+
+ Each key may have up to 16 different bindings, depending on
+ what combinations of the Shift, Lock, Control, and Meta keys
+ are depressed. For instance, in a conventional QWERTY key-
+ board mapping, pressing the ``A'' key produces a capital
+ ``A'' when the Shift or Lock key is down, an octal 001 when
+ the Control key is down, and a small ``a'' when no other key
+ is down.
+
+ The input file to _\bk_\be_\by_\bc_\bo_\bm_\bp consists of one or more lines.
+ Each line begins with an octal or decimal number designating
+ an X keyboard code. After the key code, the line should
+ contain either 1 or 16 items, each representing the binding
+ for a particular combination of the Control, Meta, Shift,
+ and Lock keys. The items should be separated by white
+ space; the format of the items is described later. The
+ bindings should be in this order:
+
+ #1 ``unshifted'': none of Shift, Lock, Control, or Meta
+ keys down
+ #2 Lock key down
+ #3 Shift key down
+ #4 Shift and Lock keys down
+ #5 Meta key down
+ #6 Meta and Lock keys down
+ #7 Meta and Shift keys down
+ #8 Meta, Shift, and Lock keys down
+ #9 Control key down
+ #10 Control and Lock keys down
+ #11 Control and Shift keys down
+ #12 Control, Shift, and Lock keys down
+
+
+
+Printed 9/15/87 18 August 1985 1
+
+
+
+
+
+
+KEYCOMP(1) UNIX Programmer's Manual KEYCOMP(1)
+
+
+
+ #13 Control and Meta keys down
+ #14 Control, Meta, and Lock keys down
+ #15 Control, Meta, and Shift keys down
+ #16 Control, Meta, Shift, and Lock keys down
+
+ If only one item is present on the line, then it represents
+ the binding for this key regardless of the positions of the
+ Control, Meta, Shift, and Lock keys.
+
+ Each item should be one of the following:
+
+ An octal or decimal number, indicating a character code
+
+ A C character literal, surrounded by single quotes.
+ Escape sequences (such as `0 or `252') are allowed, as
+ described in the C Reference Manual.
+
+ A C string literal, surrounded by double quotes. Again,
+ standard C escape sequences are allowed within the string.
+
+ The letter U, indicating ``no binding''. If there is no
+ binding, then XLookupMapping will return an empty string for
+ this key combination.
+
+ A comma may, but need not, follow each item. Whether or not
+ a comma is present, white space (spaces or tabs) must
+ separate the items. All text to the right of the 16th item
+ is ignored; comments may appear here.
+
+ Completely blank lines are ignored, as are lines beginning
+ with the '#' character. Furthermore, all text between a `#'
+ character and the following newline is ignored, provided
+ that the `#' is not part of a string enclosed in single or
+ double quotes. This allows you to place comments at the end
+ of a line that contains only a single item.
+
+ You can look at the file <_\bX/_\bX_\bk_\be_\by_\bb_\bo_\ba_\br_\bd._\bh> for a list of key
+ codes and key names of function keys.
+
+
+FILES
+ $HOME/.Xkeymap, /usr/lib/Xkeymap.txt, <X/Xkeyboard.h>
+
+SEE ALSO
+ X(1), xterm(1)
+
+DIAGNOSTICS
+ ``Couldn't fseek output file''
+ The standard output must be a file, not a pipe or a termi-
+ nal.
+
+ ``Error writing beginning of output file''
+
+
+
+Printed 9/15/87 18 August 1985 2
+
+
+
+
+
+
+KEYCOMP(1) UNIX Programmer's Manual KEYCOMP(1)
+
+
+
+ ``Error writing extension to output file''
+ _\bk_\be_\by_\bc_\bo_\bm_\bp couldn't write the output file. Maybe the file sys-
+ tem is out of space.
+
+ ``Parse error at item <number> on line <number>:
+ <message>''
+ The source file has a syntax error. Possible <message>s
+ include:
+
+ ``Line doesn't begin with key''
+ The first few characters in the line, which should be a key
+ number, were not recognizable as an octal or decimal number.
+
+ ``Keycode is too big''
+ The key at the beginning of the line was greater than 0377
+ (octal).
+
+ ``Line doesn't have 1 or 16 entries''
+ After the key, more than one but less than 16 items were
+ found. Or no items were found at all.
+
+ ``Number after backslash is too big for a character con-
+ stant''
+ In a character constant of the form `0n', the octal number
+ was greater than 377 (octal).
+
+ ``Closing single quote not found''
+ A single quote (') was encountered, but the end of the line
+ was reached before finding the matching closing single
+ quote.
+
+ ``String is too long''
+ More than 80 characters are not allowed between double
+ quotes.
+
+ ``Closing double quote not found''
+ A double quote (") was encountered, but the end of the line
+ was reached before finding the matching closing double
+ quote.
+
+ ``Too many characters for single character constant''
+ Too many characters appear between single quotes. If you
+ want to bind a key to a multiple-character sequence, use
+ double quotes.
+
+ ``Not a U, number, single- or double-quoted string''
+ _\bk_\be_\by_\bc_\bo_\bm_\bp can't parse this item; it is neither the letter U,
+ nor an octal or decimal number, nor a string enclosed in
+ single or double quotes.
+
+AUTHOR
+ Ron Newman, MIT Project Athena
+
+
+
+Printed 9/15/87 18 August 1985 3
+
+
+
+
+
+
+KEYCOMP(1) UNIX Programmer's Manual KEYCOMP(1)
+
+
+
+ Copyright 1985, 1986, Massachusetts Institute of Technology.
+ See _\bX(_\b1) for a full copyright notice.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 18 August 1985 4
+
+
+
--- /dev/null
+
+
+
+PIKAPIX(1) UNIX Programmer's Manual PIKAPIX(1)
+
+
+
+NAME
+ pikapix - recolor an X window snapshot
+
+SYNOPSIS
+ pikapix [ -s ] [ host:number ]
+
+DESCRIPTION
+ _\bP_\bi_\bk_\ba_\bp_\bi_\bx takes a snapshot of an existing window, and then
+ lets you change colors in the snapshot. This can be a con-
+ venient way to choose sets of colors for applications.
+
+ When started, _\bp_\bi_\bk_\ba_\bp_\bi_\bx grabs the mouse, and waits for you to
+ select the window you want to recolor. Clicking the right
+ button on a window selects the entire top-level window.
+ Clicking the middle button on a window selects the first
+ level subwindow under the mouse, or the top-level window if
+ there is no subwindow. Clicking the left button on a top-
+ level window selects the lowest subwindow under the mouse,
+ or the top-level window if there is no subwindow. After a
+ few moments, a snapshot of the window will appear in the
+ same place as the original window. Move the snapshot with
+ your window manager if you want to compare the snapshot with
+ the original window.
+
+ As you move the cursor around in the snapshot, it will
+ change color to reflect whatever pixel it is pointing at.
+
+ If you click the middle mouse button, you will get a popup
+ text window. The prompt indicates the current color value
+ in hexadecimal notation as described in _\bX(_\b1). To change the
+ color, simply type in a color name (or a color value in hex-
+ adecimal notation), followed by carriage return. Rubout and
+ control-U can be used for editing. To abort, simply click
+ any mouse button in the popup, or type control-C or
+ control-D.
+
+ If you click the left mouse button, you will restore the
+ color to its value in the original snapshot.
+
+ If you click the right mouse button, you will get a popup
+ mix window. At the top are three squares with the red,
+ green, and blue primaries, and at the bottom is the combined
+ color and its hexadecimal notation. Clicking the left but-
+ ton in a primary decrements its value, and clicking the
+ right button increments its value. If you press the middle
+ button in a primary and then move around, the vertical posi-
+ tion of the mouse controls the value, with zero intensity at
+ the top of the window, and full intensity at the bottom of
+ the window; releasing the mouse button sets the final value.
+ Clicking the right button in the combined color will exit
+ the popup and change to the new color. Clicking the middle
+ button in the combined color will restore the values to
+
+
+
+Printed 9/15/87 16 September 1985 1
+
+
+
+
+
+
+PIKAPIX(1) UNIX Programmer's Manual PIKAPIX(1)
+
+
+
+ their current state in the snapshot. Clicking the left but-
+ ton in the combined color will restore the values to their
+ state in the original snapshot.
+
+ Typing control-C or control-D in the snapshot will terminate
+ the program.
+
+ By default, once the snapshot is created, it no longer
+ depends on the existence of the original window, and the
+ color in the snapshot will dynamically track the color in
+ the popup mix window. However, a potentially large number
+ of color map entries may be required for this mode. If not
+ enough entries are available, the ``-s'' can be used. When
+ run with the ``-s'' option, the snapshot continues to depend
+ on colors from the original window, new colors are shared
+ when possible, and the snapshot is completely repainted
+ after every change in color.
+
+ENVIRONMENT
+ DISPLAY This program gets the display to use by default
+ from this variable.
+
+BUGS
+ Redisplay is very slow on all but small windows.
+
+AUTHOR
+ Bob Scheifler, MIT Laboratory for Computer Science.
+ Copyright (c) 1985, Massachusetts Institute of Technology
+
+SEE ALSO
+ X(1)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 16 September 1985 2
+
+
+
--- /dev/null
+
+
+
+RESIZE(1) UNIX Programmer's Manual RESIZE(1)
+
+
+
+NAME
+ resize - reset TERMCAP with current size of a window
+
+SYNOPSIS
+ resize [-u] [-s [row col]]
+
+DESCRIPTION
+ _\bR_\be_\bs_\bi_\bz_\be prints on its standard output the TERM and TERMCAP
+ commands for the C-shell of the current size of a window.
+ It is never executed directly, but should be aliased simi-
+ larly to _\bt_\bs_\be_\bt(1) to cause the C-shell to execute the com-
+ mands.
+
+ Normally, VT102 escape sequences are used. With the -s
+ option, Sun tty escape sequences are used, which has the
+ advantage that a new row and column size may be specified
+ and the window will resize appropriately.
+
+ For example, the following alias when executed as a command
+ will reset the environment of the current shell:
+
+ alias xs 'set noglob; eval `resize`'
+ alias xrs 'set noglob; eval `resize -s \!\*`'
+
+ The -u option will cause the commands to be formed appropri-
+ ately for sh (the Bourne shell) rather than csh.
+
+FILES
+ /etc/termcap for the base termcap entry to modify.
+ ~/.cshrc user's alias for the command.
+
+SEE ALSO
+ csh(1), tset(1), xterm(1)
+
+AUTHORS
+ Mark Vandevoorde (MIT-Athena), Edward Moy (Berkeley)
+ Copyright (c) 1984, 1985 by Massachusetts Institute of Tech-
+ nology.
+ See _\bX(1) for a complete copyright notice.
+
+BUGS
+ ``-u'' must appear to the left of ``-s'' if both are speci-
+ fied.
+
+ There should be some global notion of display size; termcap
+ and terminfo need to be rethought in the context of window
+ systems. (Fixed in 4.3BSD, and Ultrix-32 1.2)
+
+
+
+
+
+
+
+
+Printed 9/15/87 1 Nov 1986 1
+
+
+
--- /dev/null
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+NAME
+ uwm - Window Manager Client Application of X
+
+SYNTAX
+ uwm [-f _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be]
+
+DESCRIPTION
+ The _\bu_\bw_\bm command is a window manager client application of
+ the window server.
+
+ When the command is invoked, it traces a predefined search
+ path to locate any _\bu_\bw_\bm startup files. If no startup files
+ exist, _\bu_\bw_\bm initializes its built-in default file.
+
+ If startup files exist in any of the following locations, it
+ adds the variables to the default variables. In the case of
+ contention, the variables in the last file found override
+ previous specifications. Files in the _\bu_\bw_\bm search path are:
+
+ /_\bu_\bs_\br/_\bn_\be_\bw/_\bl_\bi_\bb/_\bX/_\bu_\bw_\bm/_\bs_\by_\bs_\bt_\be_\bm._\bu_\bw_\bm_\br_\bc
+ $_\bH_\bO_\bM_\bE/._\bu_\bw_\bm_\br_\bc
+
+ To use only the settings defined in a single startup file,
+ include the variables, resetbindings, resetmenus, resetvari-
+ ables at the top of that specific startup file.
+
+ARGUMENTS
+ -f _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ Names an alternate file as a _\bu_\bw_\bm startup file.
+
+STARTUP FILE VARIABLES
+ Variables are typically entered first, at the top of the
+ startup file. By convention, resetbindings, resetmenus, and
+ resetvariables head the list.
+
+ autoselect/noautoselect
+ places menu cursor in first menu item. If
+ unspecified, menu cursor is placed in the
+ menu header when the menu is displayed.
+
+ delta=_\bp_\bi_\bx_\be_\bl_\bs indicates the number of pixels the cursor is
+ moved before the action is interpreted by the
+ window manager as a command. (Also refer to
+ the delta mouse action.)
+
+ freeze/nofreeze
+ locks all other client applications out of
+ the server during certain window manager
+ tasks, such as move and resize.
+
+ grid/nogrid displays a finely-ruled grid to help you
+ position an icon or window during resize or
+
+
+
+Printed 9/15/87 27 January 1986 1
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ move operations.
+
+ hiconpad=_\bn indicates the number of pixels to pad an icon
+ horizontally. The default is five pixels.
+
+ hmenupad=_\bn indicates the amount of space in pixels, that
+ each menu item is padded above and below the
+ text.
+
+ iconfont=_\bf_\bo_\bn_\bt_\bn_\ba_\bm_\be
+ names the font that is displayed within
+ icons. Font names are listed in the font
+ directory, /_\bu_\bs_\br/_\bn_\be_\bw/_\bl_\bi_\bb/_\bX/_\bf_\bo_\bn_\bt.
+
+ maxcolors=_\bn limits the number of colors the window
+ manager can use in a given invocation. If set
+ to zero, or not specified, _\bu_\bw_\bm assumes no
+ limit to the number of colors it can take
+ from the color map. maxcolors counts colors
+ as they are included in the file.
+
+ normali/nonormali
+ places icons created with f.newiconify within
+ the root window, even if it is placed par-
+ tially off the screen. With nonormali the
+ icon is placed exactly where the cursor
+ leaves it.
+
+ normalw/nonormalw
+ places window created with f.newiconify
+ within the root window, even if it is placed
+ partially off the screen. With nonormalw the
+ window is placed exactly where the cursor
+ leaves it.
+
+ push=_\bn moves a window _\bn number of pixels or a rela-
+ tive amount of space, depending on whether
+ pushabsolute or pushrelative is specified.
+ Use this variable in conjunction with
+ f.pushup, f.pushdown, f.pushright, or
+ f.pushleft.
+
+ pushabsolute/pushrelative
+ pushabsolute indicates that the number
+ entered with push is equivalent to pixels.
+ When an f.push (left, right, up, or down)
+ function is called, the window is moved
+ exactly that number of pixels.
+
+ pushrelative indicates that the number
+ entered with the push variable represents a
+ relative number. When an f.push function is
+
+
+
+Printed 9/15/87 27 January 1986 2
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ called, the window is invisibly divided into
+ the number of parts you entered with the push
+ variable, and the window is moved one part.
+
+ resetbindings, resetmenus, and resetvariables
+ resets all previous function bindings, menus,
+ and variables entries, specified in any
+ startup file in the _\bu_\bw_\bm search path, includ-
+ ing those in the default environment. By
+ convention, these variables are entered first
+ in the startup file.
+
+ resizefont=_\bf_\bo_\bn_\bt_\bn_\ba_\bm_\be
+ identifies the font of the indicator that
+ displays in the corner of the window as you
+ resize windows. See the /_\bu_\bs_\br/_\bn_\be_\bw/_\bl_\bi_\bb/_\bX/_\bf_\bo_\bn_\bt
+ directory for a list of fonts.
+
+ reverse/noreverse
+ defines the display as black characters on a
+ white background for the window manager win-
+ dows and icons.
+
+ viconpad=_\bn indicates the number of pixels to pad an icon
+ vertically. Default is five pixels.
+
+ vmenupad=_\bn indicates the amount of space in pixels that
+ the menu is padded on the right and left of
+ the text.
+
+ volume=_\bn increases or decreases the base level volume
+ set by the _\bx_\bs_\be_\bt(_\b1) command. Enter an integer
+ from 0 to 7, 7 being the loudest.
+
+ zap/nozap causes ghost lines to follow the window or
+ icon from its previous default location to
+ its new location during a move or resize
+ operation.
+
+BINDING SYNTAX
+ "_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn=[_\bc_\bo_\bn_\bt_\br_\bo_\bl _\bk_\be_\by(_\bs)]:[_\bc_\bo_\bn_\bt_\be_\bx_\bt]:_\bm_\bo_\bu_\bs_\be _\be_\bv_\be_\bn_\bt_\bs:" _\bm_\be_\bn_\bu
+ _\bn_\ba_\bm_\be "
+
+ Function and mouse events are required input. Menu name is
+ required with the _\bf._\bm_\be_\bn_\bu function definition only.
+
+Function
+ f.beep emits a beep from the keyboard. Loudness is
+ determined by the volume variable.
+
+ f.circledown causes the top window that is obscuring
+ another window to drop to the bottom of the
+
+
+
+Printed 9/15/87 27 January 1986 3
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ stack of windows.
+
+ f.circleup exposes the lowest window that is obscured by
+ other windows.
+
+ f.continue releases the window server display action
+ after you stop action with the f.pause func-
+ tion.
+
+ f.focus directs all keyboard input to the selected
+ window. To reset the focus to all windows,
+ invoke _\bf._\bf_\bo_\bc_\bu_\bs from the root window.
+
+ f.iconify when implemented from a window, this function
+ converts the window to its respective icon.
+ When implemented from an icon, f.iconify con-
+ verts the icon to its respective window.
+
+ f.lower lowers a window that is obstructing a window
+ below it.
+
+ f.menu invokes a menu. Enclose `menu name' in
+ quotes if it contains blank characters or
+ parentheses.
+
+ f.menu=[_\bc_\bo_\bn_\bt_\br_\bo_\bl _\bk_\be_\by(_\bs)]:[_\bc_\bo_\bn_\bt_\be_\bx_\bt ]:_\bm_\bo_\bu_\bs_\be _\be_\bv_\be_\bn_\bt_\bs:" _\bm_\be_\bn_\bu _\bn_\ba_\bm_\be "
+
+
+ f.move moves a window or icon to a new location,
+ which becomes the default location.
+
+ f.moveopaque moves a window or icon to a new screen loca-
+ tion. When using this function, the entire
+ window or icon is moved to the new screen
+ location. The grid effect is not used with
+ this function.
+
+ f.newiconify allows you to create a window or icon and
+ then position the window or icon in a new
+ default location on the screen.
+
+ f.pause temporarily stops all display action. To
+ release the screen and immediately update all
+ windows, use the f.continue function.
+
+ f.pushdown moves a window down. The distance of the push
+ is determined by the push variables.
+
+ f.pushleft moves a window to the left. The distance of
+ the push is determined by the push variables.
+
+ f.pushright moves a window to the right. The distance of
+
+
+
+Printed 9/15/87 27 January 1986 4
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ the push is determined by the push variables.
+
+ f.pushup moves a window up. The distance of the push
+ is determined by the push variables.
+
+ f.raise raises a window that is being obstructed by a
+ window above it.
+
+ f.refresh results in exposure events being sent to the
+ window server clients for all unobscured or
+ partially obscured windows. The windows will
+ not refresh correctly if the exposure events
+ are not handled properly.
+
+ f.resize resizes an existing window. Note that some
+ clients, notably editors, react unpredictably
+ if you resize the window while the client is
+ running.
+
+ f.restartn causes the window manager application to res-
+ tart, retracing the _\bu_\bw_\bm search path and ini-
+ tializing the variables it finds.
+
+Control Keys
+ By default, the window manager uses meta as its control key.
+ It can also use ctrl, shift, lock, or null (no control key).
+ Control keys must be entered in lower case, and can be
+ abbreviated as: c, l, m, s for ctrl, lock, meta, and shift,
+ respectively.
+
+ You can bind one, two, or no control keys to a function. Use
+ the bar (|) character to combine control keys.
+
+ Note that client applications other than the window manager
+ use the shift as a control key. If you bind the shift key
+ to a window manager function, you can not use other client
+ applications that require this key.
+
+Context
+ The context refers to the screen location of the cursor when
+ a command is initiated. When you include a context entry in
+ a binding, the cursor must be in that context or the func-
+ tion will not be activated. The window manager recognizes
+ the following four contexts: icon, window, root, (null).
+
+ The root context refers to the root, or background window, A
+ (null) context is indicated when the context field is left
+ blank, and allows a function to be invoked from any screen
+ location. Combine contexts using the bar (|) character.
+
+Mouse Buttons
+
+
+
+
+Printed 9/15/87 27 January 1986 5
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ Any of the following mouse buttons are accepted in lower
+ case and can be abbreviated as l, m, or r, respectively:
+ left, middle, right.
+
+ With the specific button, you must identify the action of
+ that button. Mouse actions can be:
+
+ down function occurs when the specified button is
+ pressed down.
+
+ up function occurs when the specified button is
+ released.
+
+ delta indicates that the mouse must be moved the number
+ of pixels specified with the delta variable before
+ the specified function is invoked. The mouse can
+ be moved in any direction to satisfy the delta
+ requirement.
+
+MENU DEFINITION
+ After binding a set of function keys and a menu name to
+ f.menu, you must define the menu to be invoked, using the
+ following syntax:
+
+ menu = " _\bm_\be_\bn_\bu _\bn_\ba_\bm_\be " {
+ "_\bi_\bt_\be_\bm _\bn_\ba_\bm_\be" : "_\ba_\bc_\bt_\bi_\bo_\bn"
+ .
+ .
+ .
+ }
+
+
+ Enter the menu name exactly the way it is entered with the
+ f.menu function or the window manager will not recognize the
+ link. If the menu name contains blank strings, tabs or
+ parentheses, it must be quoted here and in the f.menu func-
+ tion entry. You can enter as many menu items as your screen
+ is long. You cannot scroll within menus.
+
+ Any menu entry that contains quotes, special characters,
+ parentheses, tabs, or strings of blanks must be enclosed in
+ double quotes. Follow the item name by a colon (:).
+
+Menu Action
+ Window manager functions
+ Any function previously described. E.g., f.move
+ or f.iconify.
+
+ Shell commands
+ Begin with an exclamation point (!) and set to run
+ in background. You cannot include a new line
+ character within a shell command.
+
+
+
+Printed 9/15/87 27 January 1986 6
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ Text strings
+ Text strings are placed in the window server's cut
+ buffer.
+
+ Strings with a new line character must begin with
+ an up arrow (^), which is stripped during the copy
+ operation.
+
+ Strings without a new line must begin with the bar
+ character (|), which is stripped during the copy
+ operation.
+
+Color Menus
+ Use the following syntax to add color to menus:
+
+ menu = "_\bm_\be_\bn_\bu _\bn_\ba_\bm_\be" (_\bc_\bo_\bl_\bo_\br_\b1:_\bc_\bo_\bl_\bo_\br_\b2:_\bc_\bo_\bl_\bo_\br_\b3:_\bc_\bo_\bl_\bo_\br_\b4) {
+ "_\bi_\bt_\be_\bm _\bn_\ba_\bm_\be" : (_\bc_\bo_\bl_\bo_\br_\b5 :_\bc_\bo_\bl_\bo_\br_\b6) : " _\ba_\bc_\bt_\bi_\bo_\bn "
+ .
+ .
+ .
+ }
+
+
+ color1 Foreground color of the header.
+
+ color2 Background color of the header.
+
+ color3 Foreground color of the highlighter, the horizon-
+ tal band of color that moves with the cursor
+ within the menu.
+
+ color4 Background color of the highlighter.
+
+ color5 Foreground color for the individual menu item.
+
+ color6 Background color for the individual menu item.
+
+Color Defaults
+ Colors default to the colors of the root window under any of
+ the following conditions:
+
+ 1) If you run out of color map entries, either before or
+ during an invocation of _\bu_\bw_\bm.
+
+ 2) If you specify a foreground or background color that
+ does not exist in the RGB color database (/_\bu_\bs_\br/_\bl_\bi_\bb/_\br_\bg_\bb._\bt_\bx_\bt)
+ both the foreground and background colors default to the
+ root window colors.
+
+ 3) If you omit a foreground or background color, both the
+ foreground and background colors default to the root window
+ colors.
+
+
+
+Printed 9/15/87 27 January 1986 7
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ 4) If the total number of colors specified in the startup
+ file exceeds the number specified in the _\bm_\ba_\bx_\bc_\bo_\bl_\bo_\br_\bs variable.
+
+ 5) If you specify no colors in the startup file.
+
+EXAMPLES
+ The following sample startup file shows the default window
+ manager options:
+
+ # Global variables
+ #
+ resetbindings;resetvariables;resetmenus
+ autoselect
+ delta=25
+ freeze
+ grid
+ hiconpad=5
+ hmenupad=6
+ iconfont=oldeng
+ menufont=timrom12b
+ resizefont=9x15
+ viconpad=5
+ vmenupad=3
+ volume=7
+ #
+ # Mouse button/key maps
+ #
+ # FUNCTION KEYS CONTEXT BUTTON MENU(if any)
+ # ======== ==== ======= ====== ============
+ f.menu = meta : :left down :"WINDOW OPS"
+ f.menu = meta : :middle down :"EXTENDED WINDOW OPS"
+ f.move = meta :w|i :right down
+ f.circleup = meta :root :right down
+ #
+ # Menu specifications
+ #
+ menu = "WINDOW OPS" {
+ "(De)Iconify": f.iconify
+ Move: f.move
+ Resize: f.resize
+ Lower: f.lower
+ Raise: f.raise
+ }
+
+ menu = "EXTENDED WINDOW OPS" {
+ Create Window: !"xterm &"
+ Iconify at New Position: f.lowericonify
+ Focus Keyboard on Window: f.focus
+ Freeze All Windows: f.pause
+ Unfreeze All Windows: f.continue
+ Circulate Windows Up: f.circleup
+ Circulate Windows Down: f.circledown
+
+
+
+Printed 9/15/87 27 January 1986 8
+
+
+
+
+
+
+UWM(1) UNIX Programmer's Manual UWM(1)
+
+
+
+ }
+
+
+RESTRICTIONS
+ The color specifications have no effect on a monochrome sys-
+ tem.
+
+FILES
+ /usr/lib/rgb.txt
+ /usr/new/lib/X/font
+ /usr/skel/.uwmrc
+ /usr/new/lib/X/uwm/system.uwmrc
+ $HOME/.uwmrc
+
+SEE ALSO
+ X(1), X(8C)
+
+AUTHOR
+ COPYRIGHT 1985, 1986
+ DIGITAL EQUIPMENT CORPORATION
+ MAYNARD, MASSACHUSETTS
+ ALL RIGHTS RESERVED.
+
+ THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE
+ WITHOUT NOTICE AND SHOULD NOT BE CONSTRUED AS A COMMITMENT
+ BY DIGITAL EQUIPMENT CORPORATION. DIGITAL MAKES NO
+ REPRESENTATIONS ABOUT THE SUITIBILITY OF THIS SOFTWARE FOR
+ ANY PURPOSE. IT IS SUPPLIED "AS IS" WITHOUT EXPRESS OR
+ IMPLIED WARRANTY.
+
+ IF THE SOFTWARE IS MODIFIED IN A MANNER CREATING DERIVATIVE
+ COPYRIGHT RIGHTS, APPROPRIATE LEGENDS MAY BE PLACED ON THE
+ DERIVATIVE WORK IN ADDITION TO THAT SET FORTH ABOVE.
+
+ Permission to use, copy, modify, and distribute this
+ software and its documentation for any purpose and without
+ fee is hereby granted, provided that the above copyright
+ notice appear in all copies and that both that copyright
+ notice and this permission notice appear in supporting docu-
+ mentation, and that the name of Digital Equipment Corpora-
+ tion not be used in advertising or publicity pertaining to
+ distribution of the software without specific, written prior
+ permission.
+
+ M. Gancarz, DEC Ultrix Engineering Group, Merrimack, New
+ Hampshire, using some algorithms originally by Bob
+ Scheifler, MIT Laboratory for Computer Science
+
+
+
+
+
+
+
+
+Printed 9/15/87 27 January 1986 9
+
+
+
--- /dev/null
+
+
+
+XCLOCK(1) UNIX Programmer's Manual XCLOCK(1)
+
+
+
+NAME
+ xclock - X Window System, analog / digital clock
+
+SYNOPSIS
+ xclock [ option ] ...
+
+DESCRIPTION
+ _\bX_\bc_\bl_\bo_\bc_\bk is the _\bX window system clock. _\bX_\bc_\bl_\bo_\bc_\bk Continuously
+ displays the current time of day. The user is given a
+ choice of either an analog or a digital display (of course
+ there is nothing precluding the user from having more
+ than one clock). It creates a window and displays the time
+ in the chosen format.
+
+ARGUMENTS
+ -analog Use analog display mode. Draw a conventional 12
+ hour clock face with ``ticks'' for each minute and
+ stroke marks on each hour. The default is digital
+ mode.
+
+ -bg _\bc_\bo_\bl_\bo_\br Determines the color of the background. The
+ default color is ``white''. On monochrome
+ displays this is ignored.
+
+ -bd _\bc_\bo_\bl_\bo_\br Determines the color of the border. The defaults
+ color is ``black''. On monochrome displays this
+ is ignored.
+
+ -bw _\bp_\bi_\bx_\be_\bl_\bs
+ Specify the width in pixels of the border around
+ the _\bx_\bc_\bl_\bo_\bc_\bk window.
+
+ -digital Use digital display mode (default). Display
+ the date and time in digital format.
+
+ -fg _\bc_\bo_\bl_\bo_\br Determines the color of the text in digital mode
+ and the tick marks in analog mode. The default
+ color is ``black''. On monochrome displays this
+ is ignored.
+
+ -hd _\bc_\bo_\bl_\bo_\br Determines the color of the hands of the clock.
+ This is ignored on monchrome displays.
+
+ -fn _\bf_\bo_\bn_\bt The specified _\bf_\bo_\bn_\bt will be used as the output font
+ in digital mode. Any fixed width font may be
+ used, the default is ``6x10''.
+
+ -help Display a brief summary of _\bx_\bc_\bl_\bo_\bc_\bk'_\bs calling syntax
+ and options.
+
+ -hl _\bc_\bo_\bl_\bo_\br Determines the color of the hands in analog mode.
+ The defaults is to make them the same as the
+
+
+
+Printed 9/15/87 4 June 1986 1
+
+
+
+
+
+
+XCLOCK(1) UNIX Programmer's Manual XCLOCK(1)
+
+
+
+ foreground color. On monochrome displays this is
+ ignored.
+
+ -padding _\bp_\bi_\bx_\be_\bl_\bs
+ Specify the width in pixels of the padding ``white
+ space'' between the window border and anything
+ _\bx_\bc_\bl_\bo_\bc_\bk displays. The default padding is 10 in
+ digital mode and 8 in analog mode.
+
+ -rv Reverses the default color values (i.e., black
+ becomes white and white becomes black).
+
+ -update _\bs_\be_\bc_\bo_\bn_\bd_\bs
+ Specify the frequency in seconds with which _\bx_\bc_\bl_\bo_\bc_\bk
+ updates its display. If the _\bx_\bc_\bl_\bo_\bc_\bk window is
+ obscured and then exposed, _\bx_\bc_\bl_\bo_\bc_\bk will override
+ this setting and redisplay immediately. The
+ default update frequency is 60 seconds. The
+ specification of an update frequency greater than
+ 30 seconds disables the display of the second
+ hand in analog mode.
+
+ -chime Cause the clock to ``chime'' once on the half hour
+ and twice on the hour.
+
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by
+ The clock window is created with the specified size
+ according to the geometry specification. See _\bX(_\b1)
+ for details. In digital mode if you do not specify
+ either height and width they are determined by the
+ font in use. In analog mode if you do not specify
+ either width or height they default to 164. The
+ default offset for any unspecified offset is -0.
+ All values are in pixels.
+
+ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by
+ Normally, _\bx_\bc_\bl_\bo_\bc_\bk gets the host and display number
+ to use from the environment variable ``DISPLAY''.
+ One can, however specify them explicitly. The
+ _\bh_\bo_\bs_\bt specifies which machine to create the _\bx_\bc_\bl_\bo_\bc_\bk
+ window on, and the _\bd_\bi_\bs_\bp_\bl_\ba_\by argument specifies the
+ display number. For example, ``mit-frobozz:1''
+ creates an _\bx_\bc_\bl_\bo_\bc_\bk on display one on the machine
+ mit-frobozz. If the host is omitted the local
+ host is assumed. If the display is omitted,
+ display 0 is assumed, the ``:'' is necessary in
+ either case.
+
+X DEFAULTS
+ Foreground
+ To determine the foreground color. Ignored on mono-
+ chrome displays.
+
+
+
+Printed 9/15/87 4 June 1986 2
+
+
+
+
+
+
+XCLOCK(1) UNIX Programmer's Manual XCLOCK(1)
+
+
+
+ Background
+ To determine the background color. Ignored on mono-
+ chrome displays.
+
+ Hands Sets the color of the hands. Ignored on monochrome
+ displays.
+
+ BorderColor or Border
+ To determine the border color. Ignored on mono-
+ chrome displays.
+
+ BorderWidth
+ To determine the border width.
+
+ BodyFont
+ To determine digital clock display font.
+
+ Highlight
+ To determine the highlight color. Ignored on mono-
+ chrome displays.
+
+ InternalBorder
+ To determine the internal padding value.
+
+ Mode To determine if ``analog'' or ``digital'' mode is
+ the default.
+
+ ReverseVideo
+ If ``on'', reverse the effect of the defaults
+ colors. Ignored on color displays.
+
+ Update To determine the update rate.
+
+ENVIRONMENT
+ DISPLAY To get the default host and display number.
+
+SEE ALSO
+ X(1), xwm(1), X(1), time(3C), select(2)
+
+AUTHORS
+ Copyright 1985, Massachusetts Institute of Technology.
+
+ Tony Della Fera (MIT-Athena, DEC)
+
+ Dave Mankins (MIT-Athena, BBN)
+
+ Ed Moy (Berkeley) added the nicer hands.
+
+BUGS
+ _\bX_\bc_\bl_\bo_\bc_\bk believes the Unix clock. When specifying the window
+ size manually in digital mode the string should be cen-
+ tered automatically, currently you have to fiddle with the
+
+
+
+Printed 9/15/87 4 June 1986 3
+
+
+
+
+
+
+XCLOCK(1) UNIX Programmer's Manual XCLOCK(1)
+
+
+
+ padding parameter to get it right.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 4 June 1986 4
+
+
+
--- /dev/null
+
+
+
+XCOLORS(1) UNIX Programmer's Manual XCOLORS(1)
+
+
+
+NAME
+ xcolors - X window system color database display
+
+SYNOPSIS
+ xcolors [ option ] ...
+
+DESCRIPTION
+ _\bx_\bc_\bo_\bl_\bo_\br_\bs displays the colors defined in _\bX window system color
+ database. _\bx_\bc_\bo_\bl_\bo_\br_\bs creates a window in which each color in
+ the database is displayed along with its name and hexade-
+ cimal rgb representation. The colors are roughly sorted by
+ color type. The mouse is used to change the colors of the
+ text, border and background by placing the cursor on the
+ color desired and clicking the left, middle or right button.
+
+ _\bx_\bc_\bo_\bl_\bo_\br_\bs understands the following options:
+
+ -bd _\bc_\bo_\bl_\bo_\br
+ Specify the border color; black is the default.
+
+ -bg _\bc_\bo_\bl_\bo_\br
+ Specify the background color; black is the default.
+
+ -bw _\bp_\bi_\bx_\be_\bl_\bs
+ Specify the width in pixels of the border around the
+ _\bx_\bc_\bo_\bl_\bo_\br_\bs window. The default value is 3 pixels.
+
+ -fg _\bc_\bo_\bl_\bo_\br
+ Specify the text color; white is the default.
+
+ -fn _\bf_\bo_\bn_\bt_\bn_\ba_\bm_\be
+ The text will be displayed in the specified font (if
+ none is specified, this defaults to 6x10).
+
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by
+ The xcolors window is created with the specified
+ size and location determined by the supplied
+ geometry specification. See _\bX(_\b1) for a full expla-
+ nation.
+
+ [_\bh_\bo_\bs_\bt]:[_\bd_\bi_\bs_\bp_\bl_\ba_\by]
+ Normally, _\bx_\bc_\bo_\bl_\bo_\br_\bs gets the host and display number
+ to use from the environment variable ``DISPLAY''.
+ Either or both can be specified with this option.
+ _\bh_\bo_\bs_\bt specifies which machine to create the _\bx_\bc_\bo_\bl_\bo_\br_\bs
+ window on, and _\bd_\bi_\bs_\bp_\bl_\ba_\by specifies the display number.
+ For example, ``hoser:0'' creates an _\bx_\bc_\bo_\bl_\bo_\br_\bs on
+ display 0 on machine hoser. Either value can be
+ defaulted by omission but ``:'' is necessary to
+ specify one or both.
+
+
+
+
+
+Printed 9/15/87 1 June 1986 1
+
+
+
+
+
+
+XCOLORS(1) UNIX Programmer's Manual XCOLORS(1)
+
+
+
+X DEFAULTS
+ Background
+ Set the background color.
+
+ BodyFont
+ Set the text font.
+
+ Highlight
+ Set the text color.
+
+ BorderWidth
+ Set the border width.
+
+ BorderColor
+ Set the border color.
+
+ENVIRONMENT
+ DISPLAY - to get the default host and display number.
+
+FILES
+ /usr/lib/rgb.txt
+
+SEE ALSO
+ X(1), xwm(1), X(8C)
+
+DIAGNOSTICS
+ Unable to open display or create window. Unable to query
+ window for dimensions. Various X errors.
+
+RESTRICTIONS
+ _\bx_\bc_\bo_\bl_\bo_\br_\bs will fail if there are fewer colors available than
+ there are color entries in the database.
+
+AUTHOR
+ John Tonry
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 1 June 1986 2
+
+
+
--- /dev/null
+
+
+
+XDEMO(1) UNIX Programmer's Manual XDEMO(1)
+
+
+
+NAME
+ xdemo - demonstration program for X window system
+
+SYNOPSIS
+ xdemo [ options ] demo [ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by ] [ _\bh_\bo_\bs_\bt:_\bn_\bu_\bm_\bb_\be_\br ]
+
+DESCRIPTION
+ _\bX_\bd_\be_\bm_\bo is a demonstration program for the X window system.
+ By default, the host and display number are extracted from
+ the environment variable ``DISPLAY''. One can, however,
+ specify a different display. _\bH_\bo_\bs_\bt specifies the host, and
+ _\bn_\bu_\bm_\bb_\be_\br specifies the number of the display. For example,
+ ``xdemo star orpheus:1'' will put the star demo on display
+ one on machine orpheus. Demo can be any of: balls, bounce,
+ circle, circles, colors, cookie, draw, life, lines, menu-
+ life, motion, plaid, qix, rgb, shades, slide, star, tetra,
+ wallpaper, web, and xor. The colors, rgb, and shades demos
+ will only work on color displays.
+
+ The window is created in the usual way using one of the
+ mouse buttons. Using the center button, depress the button
+ to define one corner of the window, move the cursor to where
+ the opposite corner of the window should be and release the
+ button. Using the right button, depress the button to
+ define the default size window, move the cursor to position
+ the window, and release the button. Using the left button
+ for all demos but colors, life, and menulife, click the left
+ button to place the default size window in the upper left
+ corner of the screen. Using the left button for the colors,
+ life, and menulife demos, depress the button to define the
+ default size window, move the cursor to position the window,
+ and release the button.
+
+ The window can also be placed, or given a default size, with
+ the standard geometry specification:
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by
+ The geometry specification can be used to set the size and
+ location of the window. See _\bX(_\b1) for details.
+
+ Most of the demos run without user input: balls, bounce,
+ circle, circles, colors, lines, plaid, qix, slide, star,
+ tetra, wallpaper, web, and xor. Most of these have random
+ number generators built in, and will produce different
+ results each time they are run, or each time the window is
+ resized.
+
+MOUSE USAGE
+ Mouse usage only applies on the demos draw, life, menulife,
+ motion, rgb, and shades.
+
+ In the draw demo, clicking the left button defines points
+ that will be connected by a spline when the center button is
+
+
+
+Printed 9/15/87 12 December 1985 1
+
+
+
+
+
+
+XDEMO(1) UNIX Programmer's Manual XDEMO(1)
+
+
+
+ clicked. If the center button is clicked twice in a row,
+ the window is cleared. Clicking the right button defines
+ points to be connected by straight lines when the center
+ button is clicked. Left and right button clicks can be com-
+ bined in a single shape. Clicking any button in one of the
+ selection boxes at the upper left selects a drawing mode:
+ patterned gray line, solid white line, solid black line,
+ dashed white line, dashed black line, filled black, filled
+ white, and filled gray. The drawing function can be
+ selected by placing the cursor over the function box at the
+ top right and typing a single hexadecimal digit (correspond-
+ ing to the characteristic function). For line drawing, the
+ brush height and width can be adjusted by placing the cursor
+ over the height or width box and typing a single hexadecimal
+ digit. Text can be put into the picture by positioning the
+ mouse and typing. The color of the text is determined from
+ the line/fill color, and the display function is applied.
+
+ The motion demo uses the mouse to define points of a shape
+ just as in the draw demo, but moves the line drawing around
+ the window, bouncing off the walls, while randomly changing
+ the points relative to each other.
+
+ The life demo uses the left button to randomly insert occu-
+ pied cells into the window and start the life program ini-
+ tially. Clicking the center button will turn life on and
+ off, so you can look at interesting intermediate patterns,
+ and the right button is used to clear the `universe'.
+
+ The menulife demo uses the left button to set/clear indivi-
+ dual cells while the button is held down. The right button
+ and the space bar can be used to single step the genera-
+ tions. The middle button pops up a pull down menu. Release
+ the middle button on a selection for it to take effect;
+ release outside of all selections to abort. Changing rules
+ takes a long time.
+
+ The rgb demo uses button operations in the three boxes at
+ the top of the window to change color values. The left but-
+ ton decrements the value, the right button increments the
+ value. If you press the middle button and then move around,
+ the vertical position of the mouse controls the value, with
+ zero intensity at the top of the box, and full intensity at
+ the bottom of the box; releasing the mouse button sets the
+ final value.
+
+ The shades demo uses button clicks to change color values.
+ A matrix of two primary colors of varying intensity, with a
+ third primary of constant intensity is displayed. The right
+ button increments the value of the third primary, the left
+ button decrements the value, and the middle button switches
+ to a different pair of initial primaries.
+
+
+
+Printed 9/15/87 12 December 1985 2
+
+
+
+
+
+
+XDEMO(1) UNIX Programmer's Manual XDEMO(1)
+
+
+
+OPTIONS
+ On color displays, colors can be specified in the command
+ line:
+
+ -fg=_\bc_\bo_\bl_\bo_\br foreground (lines, text, etc.)
+ -bg=_\bc_\bo_\bl_\bo_\br background
+ -bd=_\bc_\bo_\bl_\bo_\br border
+ -ms=_\bc_\bo_\bl_\bo_\br mouse
+ -fn=_\bf_\bo_\bn_\bt font
+
+ Many demos ignore the foreground color and do random color
+ selection.
+
+X DEFAULTS
+ For the following defaults, you can also give a demo-
+ specific default by prepending the demo name and a separat-
+ ing period, e.g., ``Plaid.Foreground''.
+
+ Background
+ To determine the background color.
+
+ Border To determine the border color.
+
+ BorderWidth
+ To determine the border width.
+
+ BodyFont
+ To determine text font.
+
+ Foreground
+ To determine the foreground color.
+
+ Mouse To determine the mouse cursor color.
+
+ MenuBackground
+ To determine the menu background color in menulife.
+
+ MenuForeground
+ To determine the menu text color in menulife.
+
+ MenuFont
+ To determine menu text font.
+
+ MenuMouse
+ To determine the menu mouse cursor color in menu-
+ life.
+
+COOKIE
+ The cookie monster wants you to give it a ``cookie'', of
+ course.
+
+
+
+
+
+Printed 9/15/87 12 December 1985 3
+
+
+
+
+
+
+XDEMO(1) UNIX Programmer's Manual XDEMO(1)
+
+
+
+ENVIRONMENT
+ DISPLAY This program gets the display to use by default
+ from this variable.
+
+AUTHOR
+ Bob Scheifler, MIT Laboratory for Computer Science. Many of
+ the demos are ripoffs: balls, bounce, circle, circles,
+ lines, plaid, slide, tetra, wallpaper, and xor were taken
+ from Lucasfilm, web was taken from Steve Ward, and qix from
+ Symbolics. Menulife written by Paul Johnson, MIT Laboratory
+ for Computer Science.
+ Copyright (c) 1985, Massachusetts Institute of Technology
+
+SEE ALSO
+ X(1), xterm(1), xwm(1)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 12 December 1985 4
+
+
+
--- /dev/null
+
+
+
+XDPR(1) UNIX Programmer's Manual XDPR(1)
+
+
+
+NAME
+ xdpr - dump an X window directly to the printer
+
+SYNOPSIS
+ xdpr [ option ]
+
+DESCRIPTION
+ _\bX_\bd_\bp_\br runs the commands _\bx_\bw_\bd(1), _\bx_\bp_\br(1),_\ba_\bn_\bd _\bl_\bp_\br(1) to dump an
+ X window, process it for the LN03 laser printer, and print
+ it out. This is the easiest way to get a printout of a win-
+ dow. _\bX_\bd_\bp_\br by default will print the largest possible
+ representation of the window on the output page.
+
+ -P_\bp_\br_\bi_\bn_\bt_\be_\br
+ The printer argument for the lpr command can be set in
+ the usual way.
+
+ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by
+ The host/display number can also be specified in the
+ usual way.
+
+ Any other arguments (not containing a ``:'' or -P ) will be
+ passed as arguments to the _\bx_\bp_\br(_\b1) command.
+
+SEE ALSO
+ xwd(1), xpr(1), xwud(1), X(1)
+
+ENVIRONMENT
+ DISPLAY - for which display to use be default.
+
+AUTHOR
+ Copyright 1985, Massachusetts Institute of Technology
+
+ Michael R. Gretzinger, MIT Project Athena
+
+ Jim Gettys, MIT Project Athena
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 27 August 1985 1
+
+
+
--- /dev/null
+
+
+
+XDVI(1) UNIX Programmer's Manual XDVI(1)
+
+
+
+NAME
+ xdvi - DVI Previewer for the X Window System
+
+SYNOPSIS
+ xdvi [-s _\bs_\bh_\br_\bi_\bn_\bk] [-p _\bp_\bi_\bx_\be_\bl_\bs] [-l] [-rv] [-fg _\bc_\bo_\bl_\bo_\br] [-bg
+ _\bc_\bo_\bl_\bo_\br] [-hl _\bc_\bo_\bl_\bo_\br] [-bd _\bc_\bo_\bl_\bo_\br] [-ms _\bc_\bo_\bl_\bo_\br] [=_\bg_\be_\bo_\bm_\be_\bt_\br_\by]
+ [_\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by] file
+
+DESCRIPTION
+ _\bX_\bd_\bv_\bi is a program which runs under the X window system. It
+ is used to preview DVI files, such as produced by TeX.
+
+ The -p option defines the pixels per inch for font selec-
+ tion. Default value is 300.
+
+ The -s option defines the initial shrink factor. Default
+ value is 4.
+
+ The -l option causes used fonts to be listed on diagnostic
+ output.
+
+MOUSE
+ Clicking the right button will display the next page.
+ Clicking the left button will display the previous page.
+ Clicking the right button with the Shift key held down will
+ display the next window full to the right. Clicking the
+ left button with the Shift key held down will display the
+ previous window full to the left. Clicking the middle but-
+ ton will display the next window full down. Clicking the
+ middle button with the Shift key held down will display the
+ next window full up.
+
+KEYBOARD
+ You can exit the program by typing `q', control-C, or
+ control-D. You can move to the next page with `n', `f', or
+ SPACE. You can move the the previous page with `p', `b', or
+ control-H. You can move up a window-full with `u', down
+ with `d', left with `l', and right with `r'. You can change
+ the shrink factor by typing in the number (one or more
+ digits), followed by `s'. If you type `s' without a number,
+ the smallest factor that makes the entire page fit in the
+ window will be used. You can force redisplay with control-
+ L. You can move a relative number of pages by typing an
+ optional `-', a number (one or more digits) and then car-
+ riage return or line feed. You can move to a specific page
+ by typing a number (one or more digits) and then `g'. You
+ can move to the last page by typing `g' without a number.
+
+X DEFAULTS
+ Accepts the following defaults:
+
+
+
+
+
+Printed 9/15/87 4 January 1986 1
+
+
+
+
+
+
+XDVI(1) UNIX Programmer's Manual XDVI(1)
+
+
+
+ BorderWidth
+ Set the border width of the window.
+
+ ReverseVideo
+ If ``on'', reverse the definition of foreground and
+ background color.
+
+ Foreground
+ Set the text/graphics color.
+
+ Background
+ Set the background color.
+
+ Border Set the border color.
+
+ Highlight
+ Set the page border color.
+
+ Mouse Set the mouse cursor color.
+
+ENVIRONMENT
+ Uses the environment variable ``DISPLAY'' to specify which
+ bit map display terminal to use.
+
+SEE ALSO
+ X(1).
+
+AUTHOR
+ Eric Cooper, CMU, did a version for direct output to a QVSS.
+ Modified for X by Bob Scheifler, MIT Laboratory for Computer
+ Science.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 4 January 1986 2
+
+
+
--- /dev/null
+
+
+
+XFAX(1) UNIX Programmer's Manual XFAX(1)
+
+
+
+NAME
+ xfax - display a FAX file in an X window
+
+SYNOPSIS
+ xfax [ options ] [ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by ] [ _\bh_\bo_\bs_\bt:_\bn_\bu_\bm_\bb_\be_\br ] file
+
+DESCRIPTION
+ _\bX_\bf_\ba_\bx displays a Dacom 450/500 Facsimile file (see NIC RFC
+ 803) in an X window. By default, the host and display
+ number are extracted from the environment variable
+ ``DISPLAY'', but one can specify a different host in the
+ command line. The window is created in the usual way using
+ a geometry specification or using a mouse button. Clicking
+ left creates a full screen window. With the center button,
+ depress the button to define one corner of the window, move
+ the cursor to where the opposite corner of the window should
+ be and release the button.
+
+ Decoding the file usually takes no more than a minute, and
+ then the file is displayed. You can move around in the file
+ by pressing the center button in one spot, moving somewhere,
+ and releasing the button. The spot you pointed at first
+ will move to the spot you pointed at last.
+
+OPTIONS
+ On color displays, colors can be specified in the command
+ line:
+
+ -fg=_\bc_\bo_\bl_\bo_\br foreground
+ -bg=_\bc_\bo_\bl_\bo_\br background
+ -bd=_\bc_\bo_\bl_\bo_\br border
+ -ms=_\bc_\bo_\bl_\bo_\br mouse
+
+X DEFAULTS
+ Background
+ To determine the background color.
+
+ Border To determine the border color.
+
+ BorderWidth
+ To determine the border width.
+
+ Foreground
+ To determine the foreground color.
+
+ Mouse To determine the mouse cursor color.
+
+ENVIRONMENT
+ DISPLAY This program gets the display to use by default
+ from this variable.
+
+
+
+
+
+Printed 9/15/87 12 December 1985 1
+
+
+
+
+
+
+XFAX(1) UNIX Programmer's Manual XFAX(1)
+
+
+
+AUTHOR
+ Bob Scheifler, MIT Laboratory for Computer Science.
+ Copyright (c) 1985, Massachusetts Institute of Technology
+
+SEE ALSO
+ X(1)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 12 December 1985 2
+
+
+
--- /dev/null
+
+
+
+XFD(1) UNIX Programmer's Manual XFD(1)
+
+
+
+NAME
+ xfd - X window system font displayer
+
+SYNOPSIS
+ xfd [ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by ] [ _\bh_\bo_\bs_\bt:_\bn_\bu_\bm_\bb_\be_\br ] [ options ] fontname
+
+DESCRIPTION
+ _\bX_\bf_\bd creates a window which displays all characters in the
+ named font. The characters are displayed in increasing
+ ASCII order, 8 to a line, from the first to the last charac-
+ ter defined in the font.
+
+ The font name is interpreted by the X server. On a VAX, if
+ the name does not begin with ``/'', the X server adds the
+ suffix ``.onx'' to it and looks up the font file in the
+ directory /_\bu_\bs_\br/_\bn_\be_\bw/_\bl_\bi_\bb/_\bX/_\bf_\bo_\bn_\bt/. If the name does begin with
+ ``/'', the X server treats it as an absolute pathname of a
+ file containing a font.
+
+ If no font name is given on the command line, _\bx_\bf_\bd displays
+ the font ``vtsingle''.
+
+ The window stays around until the xfd process is killed or
+ a mouse button is pressed on the window.
+
+OPTIONS
+ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by
+ Normally, _\bx_\bf_\bd gets the host and display number to
+ use from the environment variable ``DISPLAY''. One
+ can, however specify them explicitly. The _\bh_\bo_\bs_\bt
+ specifies which machine to create the window on, and
+ the _\bd_\bi_\bs_\bp_\bl_\ba_\by argument specifies the display number.
+ For example, ``orpheus:1'' creates a shell window on
+ display one on the machine orpheus.
+
+ -bw _\bb_\bo_\br_\bd_\be_\br_\bw_\bi_\bd_\bt_\bh
+ Allows you to specify the width of the window border
+ in pixels.
+
+ -rv The screen will be displayed with black characters
+ on a white background, rather than the default white
+ on black.
+
+ -fg _\bc_\bo_\bl_\bo_\br
+ On color displays, determines the color of the text.
+
+ -bg _\bc_\bo_\bl_\bo_\br
+ On color displays, determines the color of the back-
+ ground.
+
+ -bd _\bc_\bo_\bl_\bo_\br
+ On color displays, determines the color of the
+
+
+
+Printed 9/15/87 1 January 1986 1
+
+
+
+
+
+
+XFD(1) UNIX Programmer's Manual XFD(1)
+
+
+
+ border.
+
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by
+ _\bX_\bf_\bd will also take a standard geometry specification
+ (see X(1)).
+
+X DEFAULTS
+ _\bX_\bf_\bd uses a number of standard default values.
+
+ BorderWidth
+ Set the border width of the window.
+
+ BorderColor
+ Set the border color of the window.
+
+ ReverseVideo
+ If ``on'', reverse the definition of foreground and
+ background color.
+
+ Foreground
+ Set the text color.
+
+ Background
+ Set the background color.
+
+FILES
+ /usr/new/lib/X/font/*.onx
+
+SEE ALSO
+ X(1), X(8C), xterm(1)
+
+ENVIRONMENT
+ DISPLAY - To find out which X you are using.
+
+BUGS
+ It should display the name of the font somewhere.
+
+AUTHORS
+ Ron Newman, MIT Project Athena, Jim Gettys, DEC, MIT Project
+ Athena
+ Copyright (c) 1984, 1985 by Massachusetts Institute of Tech-
+ nology.
+ See X(1) for a complete copyright notice.
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 1 January 1986 2
+
+
+
--- /dev/null
+
+
+
+XHOST(1) UNIX Programmer's Manual XHOST(1)
+
+
+
+NAME
+ xhost - X window system access control program
+
+SYNOPSIS
+ xhost [+-]host ...
+
+DESCRIPTION
+ _\bX_\bh_\bo_\bs_\bt is used to add and delete hosts to the list of
+ machines X will accept connections from. This is an elemen-
+ tary form of privacy control, since otherwise X would be
+ willing to create windows for anyone on the internet. It is
+ only sufficient for a workstation (single user) environment,
+ though it does limit the worst abuses.
+
+ If you want to set up hosts that you always trust, you can
+ specify them in your login file, or you can specify the
+ hosts in the file /_\be_\bt_\bc/_\bX*._\bh_\bo_\bs_\bt_\bs, where * is the number of
+ the display on the machine.
+
+ Specifying a host name (with an optional leading plus sign)
+ adds that host to the list; use a leading minus sign to
+ delete a host.
+
+ DECnet nodes should be specified as names with trailing
+ ``::''.
+
+ This program can only be executed on the machine the display
+ is connected to.
+
+ It is possible to remove the current host from the access
+ list. Be warned that you can't undo this without logging
+ out.
+
+ _\bX_\bh_\bo_\bs_\bt with no arguments will print the current hosts allowed
+ to access your display.
+
+FILES
+ /etc/X*.hosts
+
+SEE ALSO
+ X(8C), xterm(1)
+
+ENVIRONMENT
+ DISPLAY - To find out which X you are using.
+
+AUTHOR
+ Copyright 1985 by Massachusetts Institute of Technology.
+ See _\bX(_\b1) for a complete copyright notice.
+ Bob Scheifler, MIT Laboratory for Computer Science, Jim Get-
+ tys, MIT Project Athena (DEC).
+
+
+
+
+
+Printed 9/15/87 25 January 1986 1
+
+
+
--- /dev/null
+
+
+
+XIMPV(1) UNIX Programmer's Manual XIMPV(1)
+
+
+
+NAME
+ ximpv - Imprint (Impress) Previewer for the X Window System
+
+SYNOPSIS
+ ximpv [=_\bg_\be_\bo_\bm_\be_\bt_\br_\by] [-p#] [-rv] [-fg _\bc_\bo_\bl_\bo_\br] [-bg _\bc_\bo_\bl_\bo_\br] [-bd
+ _\bc_\bo_\bl_\bo_\br] [-ms _\bc_\bo_\bl_\bo_\br] [_\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by] file
+
+DESCRIPTION
+ _\bX_\bi_\bm_\bp_\bv is a program which runs under the X window system. It
+ is used to preview images which is destined for an Imagen
+ laser printer.
+
+ The -_\bp# option, if used, will set the number of pages you
+ can back up to #. Default is five pages. Zero (or no number)
+ runs faster as the pages do not have to be transferred to
+ disk.
+
+ If the _\bf_\bi_\bl_\be given to ximpv is correct a square will appear
+ on the screen indicating text is about to appear. If no
+ _\bf_\bi_\bl_\be is given stdin must be from a pipe or an error message
+ is printed and the program aborted.
+
+ The pages of the file are displayed in the order. Only
+ about 2/3 of a page can be displayed at once (this is
+ because of aspect ratio differences).
+
+ARGUMENTS
+ -bd _\bc_\bo_\bl_\bo_\br
+ Specify the border color.
+
+ -ms _\bc_\bo_\bl_\bo_\br
+ Specify the mouse color.
+
+ -fg _\bc_\bo_\bl_\bo_\br
+ Specify the foreground color.
+
+ -bg _\bc_\bo_\bl_\bo_\br
+ Specify the background color.
+
+ -bw _\bw_\bi_\bd_\bt_\bh
+ Specify the width of the border.
+
+ -rv Cause _\bx_\bi_\bm_\bp_\bv to produce all output in black-on-white
+ instead of white-on-black.
+
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by
+ The previewer window is created with the specified
+ size specified by the geometry specification. See
+ _\bX(_\b1) for details of this specification.
+
+MOUSE
+
+
+
+
+Printed 9/15/87 30 August 1985 1
+
+
+
+
+
+
+XIMPV(1) UNIX Programmer's Manual XIMPV(1)
+
+
+
+ Clicking the right button will display the next window full,
+ moving to the next page as needed. Clicking the middle but-
+ ton will move to the opposite end of the current page.
+ Clicking the left button will display the previous window
+ full, moving to the previous page as needed.
+
+ Clicking the right button with the Shift key held down will
+ display the next window full to the right. Clicking the
+ middle button with the Shift key held down will move to the
+ opposite side of the current page. Clicking the left button
+ with the Shift key held down will display the previous win-
+ dow full to the left.
+
+KEYBOARD
+ The user may move up and down the page with the numeric pad
+ keys:
+ fine medium coarse
+ up page 7 8 9
+
+ down page 1 2 3
+ The numeric pad keys can also be used for horizontal motion:
+ left center right
+ horizontal 4 5 6
+
+ You may also move forward or back in the document by using:
+ - for back a page,
+ up-arrow for back a window full,
+ . for forward a page,
+ down-arrow for forward a window full,
+ , or + for forward to next new page.
+ You may also move left and right in the document by small
+ amounts using the left and right arrow keys.
+ The only other functional keys are the CNTRL -D key and the
+ CNTRL -C key, which exit the program.
+
+X DEFAULTS
+ Accepts the following defaults:
+
+ BorderWidth
+ Set the border width of the window.
+
+ ReverseVideo
+ If ``on'', reverse the definition of foreground and
+ background color.
+
+ Foreground
+ Set the text/graphics color.
+
+ Background
+ Set the background color.
+
+
+
+
+
+Printed 9/15/87 30 August 1985 2
+
+
+
+
+
+
+XIMPV(1) UNIX Programmer's Manual XIMPV(1)
+
+
+
+ Border Set the border color.
+
+ Mouse Set the mouse cursor color.
+
+SEE ALSO
+ X(1), xproof(1), xdvi(1)
+
+ENVIRONMENT
+ Uses the environment variable ``DISPLAY'' to specify which
+ bit map display terminal to use.
+
+FILES
+ /usr/tmp/impvXXXXXX circular buffer of screen images
+
+SEE ALSO
+ X(1).
+
+AUTHOR
+ Steven Sutphen and Ted Bentley, University of Alberta
+ Changes and enhancements for X by Bob Scheifler, MIT Labora-
+ tory for Computer Science, and Jim Gettys, DEC, Project
+ Athena.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 30 August 1985 3
+
+
+
--- /dev/null
+
+
+
+XINIT(1) UNIX Programmer's Manual XINIT(1)
+
+
+
+NAME
+ xinit - X window system initializer
+
+SYNOPSIS
+ xinit [[client] options] [-- [server] [display] options]
+
+DESCRIPTION
+ _\bX_\bi_\bn_\bi_\bt is intended to be used when the X window system server
+ is not run automatically from _\bi_\bn_\bi_\bt(_\b8), and the window system
+ must be started from a shell running on the display. This
+ might be true, for example, if a normal login is run in a
+ glass-tty emulator on a workstation console, so that dif-
+ ferent window systems can easily be run on the display at
+ different times.
+
+ _\bX_\bi_\bn_\bi_\bt starts up the server and a single client application,
+ which is typically _\bx_\bt_\be_\br_\bm(_\b1). When the client eventually
+ terminates, _\bx_\bi_\bn_\bi_\bt automatically kills off the server and
+ then itself terminates.
+
+ By default, _\bx_\bi_\bn_\bi_\bt expects the server to exist in an execut-
+ able named ``X'' in the search path, and for _\bx_\bt_\be_\br_\bm(_\b1) to
+ also exist in the search path. It starts up the X server on
+ display 0, and then starts up
+ xterm =+1+1 -n login unix:0
+
+ A different client and/or server can be specified in the
+ command line, and command line options can be passed to both
+ the server and the client. The client and its options come
+ first in the command line. The server and its options must
+ be preceded by ``--''. If the first argument to xinit
+ begins with `/' or a letter, it is taken to be the client
+ program to use instead of xterm, and none of the default
+ xterm options are used. Otherwise, the first and subsequent
+ arguments are simply appended as further options to the
+ default _\bx_\bt_\be_\br_\bm command line.
+
+ Following the ``--'' argument, if the next argument begins
+ with `/' or a letter, it is taken to be the server program
+ to use instead of ``X''. If the next argument begins with a
+ digit, it is taken to be the display number; otherwise
+ display 0 is assumed. The remaining arguments are added as
+ options to the server command line.
+
+ Examples:
+
+ xinit =80x65+10+10 -fn 8x13 -j -fg white -bg navy
+ xinit -e widgets -- Xsun -l -c
+ xinit rsh fasthost cpupig workstation:1 -- 1 -a 2 -t 5
+
+AUTHOR
+ Copyright (c) 1986 by Massachusetts Institute of Technology.
+
+
+
+Printed 9/15/87 25 January 1986 1
+
+
+
+
+
+
+XINIT(1) UNIX Programmer's Manual XINIT(1)
+
+
+
+ See _\bX(_\b1) for a complete copyright notice.
+ Bob Scheifler, MIT Laboratory for Computer Science
+
+SEE ALSO
+ X(8C), xterm(1)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 25 January 1986 2
+
+
+
--- /dev/null
+
+
+
+XLOAD(1) UNIX Programmer's Manual XLOAD(1)
+
+
+
+NAME
+ xload - X window system load average display
+
+SYNOPSIS
+ xload [ option ] ...
+
+DESCRIPTION
+ _\bx_\bl_\bo_\ba_\bd continuously displays the system load average under
+ the _\bX window system. _\bx_\bl_\bo_\ba_\bd creates a window in which the
+ load average is represented as a bar graph with n divisions.
+ Each division represents one unit of load average. The name
+ of the host is displayed in the upper left corner.
+
+ _\bx_\bl_\bo_\ba_\bd understands the following options:
+
+ -bd _\bc_\bo_\bl_\bo_\br
+ Specify the border color. On monochrome displays
+ this option is ignored. The default color is
+ ``black''.
+
+ -bg _\bc_\bo_\bl_\bo_\br
+ Specify the background color. On monochrome
+ displays this option is ignored. The default color
+ is ``white''.
+
+ -bw _\bp_\bi_\bx_\be_\bl_\bs
+ Specify the width in pixels of the border around the
+ _\bx_\bl_\bo_\ba_\bd window. The default value is 3 pixels.
+
+ -fg _\bc_\bo_\bl_\bo_\br
+ Specify the graph color. On monochrome displays
+ this option is ignored. The default color is
+ ``black''.
+
+ -fn _\bf_\bo_\bn_\bt_\bn_\ba_\bm_\be
+ The hostname will be displayed in the specified font
+ (if none is specified, this defaults to 6x10).
+
+ -hl _\bc_\bo_\bl_\bo_\br
+ Specify the hostname and scale line color; the
+ default is to make it the same as the graph color.
+
+ -rv Reverses the default color values (i.e., black
+ becomes white and white becomes black).
+
+ -fw Forces the default color values to remain at their
+ predetermined settings (i.e., white is white and
+ black is black).
+
+ -scale _\bi_\bn_\bt_\be_\bg_\be_\br
+ Specify the minimum number of divisions on the graph
+ (default 1). _\bX_\bl_\bo_\ba_\bd is free to use more divisions if
+
+
+
+Printed 9/15/87 18 August 1985 1
+
+
+
+
+
+
+XLOAD(1) UNIX Programmer's Manual XLOAD(1)
+
+
+
+ the load gets too high to display, but it will never
+ use fewer divisions than this.
+
+ -update _\bs_\be_\bc_\bo_\bn_\bd_\bs
+ Specify the frequency in seconds with which _\bx_\bl_\bo_\ba_\bd
+ updates its display (except if the _\bx_\bl_\bo_\ba_\bd window is
+ obscured and then exposed, immediate redisplay
+ occurs). The default update frequency is 5 seconds.
+ Specification of a frequency less than 5 seconds is
+ ignored and the default frequency is used instead.
+
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by
+ The load graph window is created with the specified
+ size and location determined by the supplied
+ geometry specification. See _\bX(_\b1) for a full expla-
+ nation.
+
+ [_\bh_\bo_\bs_\bt]:[_\bd_\bi_\bs_\bp_\bl_\ba_\by]
+ Normally, _\bx_\bl_\bo_\ba_\bd gets the host and display number to
+ use from the environment variable ``DISPLAY''.
+ Either or both can be specified with this option.
+ _\bh_\bo_\bs_\bt specifies which machine to create the _\bx_\bl_\bo_\ba_\bd
+ window on, and _\bd_\bi_\bs_\bp_\bl_\ba_\by specifies the display number.
+ For example, ``mit-grape-nehi:0'' creates an _\bx_\bl_\bo_\ba_\bd
+ on display 0 on machine mit-grape-nehi. Either value
+ can be defaulted by omission but ``:'' is necessary
+ to specify one or both.
+
+X DEFAULTS
+ Foreground
+ Set the graph color. Ignored on monochrome
+ displays.
+
+ Background
+ Set the background color. Ignored on monochrome
+ display.
+
+ BodyFont
+ Set the hostname font.
+
+ Border Set the internal border padding.
+
+ BorderColor
+ Set the border color. Ignored on monochrome
+ displays.
+
+ BorderWidth
+ Set the border width of the window.
+
+ Highlight
+ Set the hostname and scale line color. Ignored on
+ monochrome displays.
+
+
+
+Printed 9/15/87 18 August 1985 2
+
+
+
+
+
+
+XLOAD(1) UNIX Programmer's Manual XLOAD(1)
+
+
+
+ ReverseVideo
+ If ``on'', reverse the effect of the defaults
+ colors. Ignored on color displays.
+
+ Scale Set the minimum scale.
+
+ Update Set the update interval.
+
+ENVIRONMENT
+ DISPLAY - to get the default host and display number.
+
+SEE ALSO
+ X(10, xwm(1), X(8C), mem(4), select(2)
+
+DIAGNOSTICS
+ Unable to open display or create window. Unable to open
+ /dev/kmem. Unable to query window for dimensions. Various X
+ errors.
+
+BUGS
+ _\bx_\bl_\bo_\ba_\bd requires the ability to open and read /dev/kmem. On
+ most systems, this requires the suid bit set with root own-
+ ership or the sgid bit set and membership in the same group
+ as /dev/kmem.
+
+AUTHORS
+ K. Shane Hartman (MIT-LCS), Stuart A. Malone (MIT-LCS)
+ Host name feature added by Jim Gettys (MIT-Athena). Scale
+ feature added by Bob Scheifler (MIT-LCS). Automatic rescal-
+ ing feature added by Stuart A. Malone (MIT-LCS). Color
+ enhancements added by Tony Della Fera (MIT-Athena)
+ Copyright (c) 1985, Massachusetts Institute of Technology.
+ See X(1) for a complete copyright notice.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 18 August 1985 3
+
+
+
--- /dev/null
+
+
+
+XNWM(1) UNIX Programmer's Manual XNWM(1)
+
+
+
+NAME
+ xnwm - X window system manager process
+
+SYNOPSIS
+ xnwm [ -cmsnftv2 ] [ @_\bb_\bo_\br_\bd_\be_\br ] [ %_\bi_\bc_\bo_\bn_\bD_\be_\bl_\bt_\ba ]
+ [ fm=_\bf_\bo_\bn_\bt ] [ fi=_\bf_\bo_\bn_\bt ] [ fs=_\bf_\bo_\bn_\bt ]
+ [ l=_\bo_\bp ] [ m=_\bo_\bp ] [ r=_\bo_\bp ]
+ [ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by ] [ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by ]
+
+DESCRIPTION
+ The window manager is a process that allows the user of a
+ display running the X window system to manipulate the win-
+ dows on the screen. X implements the `desktop model' of
+ overlapping windows; _\bx_\bn_\bw_\bm allows windows to be moved, iconi-
+ fied, and resized, allows the order of the windows in the
+ `stack' of overlapping windows to be manipulated, and allows
+ the keyboard focus to be attached to a window. X allows
+ windows to contain other windows, but _\bx_\bn_\bw_\bm only manipulates
+ the top-level windows and not any of the subwindows.
+
+ _\bX_\bn_\bw_\bm takes arguments _\bh_\bo_\bs_\bt and _\bd_\bi_\bs_\bp_\bl_\ba_\by, which refer the the
+ host and display number. For example `xnwm amadeus:1' would
+ start up the window manager on display one on the machine
+ amadeus. By default, _\bx_\bn_\bw_\bm uses the host and display number
+ stored in the environment variable DISPLAY, and therefore
+ they are not normally specified.
+
+ _\bX_\bn_\bw_\bm has 2 modes of operation, `normal' and `popup', In
+ normal mode _\bx_\bn_\bw_\bm creates a menu window across the top of the
+ screen. To perform an action, you click any mouse button in
+ the appropriate menu box and then click the same button in
+ the window you wish to affect. _\bX_\bn_\bw_\bm also reserves certain
+ button/key combinations and interprets them as operations on
+ existing windows. The key combination is specified in the
+ command line with some subset of the options: -c (Control),
+ -m (Meta), and -s (Shift). For example, if you specify the
+ options -cm then the Control and Meta keys must be down at
+ the time a mouse button is depressed. The option -n (None)
+ means that no buttons need be held down. This is
+ discouraged since it means that applications will never
+ receive unshifted mouse clicks. If no combination is speci-
+ fied in the command line, Meta is assumed. Note: the key
+ combination is not necessary when using functions from the
+ menu; it is only needed with the assigned button functions
+ to distinguish window manager operations from operations
+ destined for the application running within the window.
+
+ The window manager normally takes control of the screen at
+ various times to assure that the screen image remains
+ correct while performing window manager operations. When
+ this happens, requests from other applications are tem-
+ porarily suspended until the window manager finishes the
+
+
+
+Printed 9/15/87 19 July 1985 1
+
+
+
+
+
+
+XNWM(1) UNIX Programmer's Manual XNWM(1)
+
+
+
+ operation. The option -f (no freeze) disables this. If
+ this option is specified, window outlines for _\bM_\bo_\bv_\be and
+ _\bR_\be_\bs_\bi_\bz_\be will flicker rather than remaining solid, and the
+ background behind popup windows (see later) will take longer
+ to redraw.
+
+ The options -t (thin), -v (vertical), and -2 (2 rows) con-
+ trol the format of the menu bar. In the absence of any of
+ these, the menu extends across the entire screen. If the -t
+ option is given, the menu bar will not extend fully across
+ the screen; instead there will be room at the right (con-
+ venient for, for example, a clock window). If the -v option
+ is used, the menu windows are stacked vertically instead of
+ spread horizontally. The -2 option causes the menu windows
+ to be in two rows, allowing room for a terminal window the
+ height of the screen while still allowing menu access.
+ Either of the last two options automatically selects the -t
+ option. The menu is located in the upper left corner of the
+ screen by default, but its location can be set with the
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by option as usual with X applications. (Notice that
+ there is no size component, position information is used
+ only.)
+
+ _\bX_\bn_\bw_\bm will use reverse video for the menu, the cursor, icon
+ text, and the frame around selected windows if the -r
+ (reverse) option is used.
+
+ The border width around selected windows can be changed with
+ the @ argument; the default is 5 pixels.
+
+ The default font for displaying text is ``8x13''. You can
+ specify a different font with the fm= (Menu font), fi= (Icon
+ font), and the fs= (Size window font) options.
+
+ Initially, the left, middle, and right mouse buttons are
+ bound to the operations _\bS_\be_\bl_\be_\bc_\bt, _\bR_\ba_\bi_\bs_\be, and _\bM_\bo_\bv_\be. You can
+ change these bindings with the l= (left), m= (middle), and
+ r= (right) arguments. Each should be followed by one of the
+ letters "srmilzc", representing, respectively, _\bS_\be_\bl_\be_\bc_\bt,
+ _\bR_\ba_\bi_\bs_\be, _\bM_\bo_\bv_\be, _\bI_\bc_\bo_\bn_\bi_\bf_\by, _\bL_\bo_\bw_\be_\br, _\br_\be_\bs_\bi_\bZ_\be, and _\bC_\bi_\br_\bc_\bu_\bl_\ba_\bt_\be. They may
+ also be followed by nothing, in which case no function is
+ bound to that key.
+
+ Clicking any button that is not bound to the _\bS_\be_\bl_\be_\bc_\bt function
+ in the background will cause the menu window to become visi-
+ ble if it has become covered by other windows. Double
+ clicking the background will cause the menu to move back to
+ its original position.
+
+ In popup mode, the menu window is not normally displayed,
+ but instead `pops up' when a particular button is pressed.
+ To get popup mode, bind the letter ``p'' to any of the three
+
+
+
+Printed 9/15/87 19 July 1985 2
+
+
+
+
+
+
+XNWM(1) UNIX Programmer's Manual XNWM(1)
+
+
+
+ buttons as described above. (You may also bind the other
+ buttons as desired.) Whenever the bound button is clicked
+ while the appropriate combination of control, meta, and
+ shift keys is depressed, or any time a button that is not
+ bound to the _\bS_\be_\bl_\be_\bc_\bt function is clicked in the background,
+ the menu will appear beneath the cursor. You may then
+ select any menu function you wish; after the operation is
+ completed the menu will disappear. To make the menu disap-
+ pear without performing any operation, just move the cursor
+ out of the menu area. Note: the mouse button bound to the
+ popup function may not be rebound using Assign. Using popup
+ mode with complicated screen images and with no freeze (the
+ -f option) may cause some difficulties if the menu obscures
+ the image, since the applications will have to redraw their
+ windows after the menu goes away.
+
+ The available commands are described below. For any of
+ these commands, if you press a button to start a command,
+ and then want to abort the command, simply press one of the
+ other buttons before releasing the first button.
+
+ Select attaches the keyboard to a window, i.e., keyboard
+ input will go to that window (hierarchy) even when the mouse
+ is outside the window. It also Raises the selected window.
+ Selecting the background will detach the keyboard from any
+ window (actually, it attaches it to the background window).
+ If no window is selected the keyboard input will go to the
+ window which currently contains the mouse cursor. The
+ selected window is highlighted by drawing a partial frame
+ around the window. Selecting an icon allows the icon name
+ to be edited: the delete key deletes the last character,
+ control-U deletes the entire name, and other characters are
+ appended to the current name. Typing a return restores the
+ input focus to the most recent non-icon window selected.
+
+ Raise raises the window to the top of any stack of overlap-
+ ping windows.
+
+ Move is used to move a window. If you apply it to a window,
+ an outline will be moved with the mouse; when you release
+ the button, the window will be moved.
+
+ (De)Iconify will make a window into an icon. If the mouse
+ is moved more than a threshold amount, or this is the first
+ time the window has been iconified, the icon will appear at
+ the location on the screen where the button is released.
+ Otherwise, the icon will reappear at its previous location.
+ This threshold may be changed with the %_\bi_\bc_\bo_\bn_\bD_\be_\bl_\bt_\ba option.
+ Giving a negative value will disable this effect. The
+ default is 5 pixels. (De)Iconify will make the original
+ window reappear at its former position on the screen if it
+ is applied to an icon. The name displayed in the icon can
+
+
+
+Printed 9/15/87 19 July 1985 3
+
+
+
+
+
+
+XNWM(1) UNIX Programmer's Manual XNWM(1)
+
+
+
+ be edited by Selecting the icon.
+
+ Lower will `push' the window you point at to the bottom of
+ any stack of overlapping windows.
+
+ Resize is used to resize a window by moving a corner or an
+ edge. If you apply it to a window, a rubber banded outline
+ of the window will be displayed and moving the mouse will
+ change its size, leaving the opposite corner or other edges
+ fixed. The corner or edge to be moved depends on the where
+ the mouse is when the button is pressed. Imagine the window
+ divided with grid of nine rectangles. If the mouse is in
+ one of the four corner rectangles or the center rectangle,
+ then the corner closest to the mouse will be moved; other-
+ wise, the closest edge will be moved. When the button is
+ released, the window will be resized.
+
+ Circulate causes the lowest window in the stack of overlap-
+ ping windows to be Raised ; successive applications will
+ reveal every window in turn.
+
+ Assign allows you to change the button bindings; to use it
+ click any button in the Assign menu window and then click
+ the same button in any other function to assign that func-
+ tion to that button. To remove the assignment from a but-
+ ton, double click the Assign window.
+
+X DEFAULTS AND OPTION SUMMARY
+ MenuFont (fm=_\bn_\ba_\bm_\be)
+ Set the default font for the menu.
+
+ SizeFont (fs=_\bn_\ba_\bm_\be)
+ Set the default font for the size window.
+
+ IconFont (fi=_\bn_\ba_\bm_\be)
+ Set the default font for icons.
+
+ FrameWidth (@_\bv_\ba_\bl_\bu_\be)
+ Set the width of the frame around selected windows.
+
+ IconifyDelta (%_\bv_\ba_\bl_\bu_\be)
+ Set the threshold for moving icons.
+
+ ReverseVideo (-r)
+ Sets reverse video for the menu, icons, selection
+ border, and cursor.
+
+ MenuFormat (-tv2)
+ Sets the format of the menu; should be some subset
+ of tv2 meaning thin, vertical, or 2 rows.
+
+ Freeze (-f)
+
+
+
+Printed 9/15/87 19 July 1985 4
+
+
+
+
+
+
+XNWM(1) UNIX Programmer's Manual XNWM(1)
+
+
+
+ If set to ``off'', disables _\bx_\bn_\bw_\bm taking control of
+ the screen during operations.
+
+ KeyCombination (-csmln)
+ Sets the keys required to specify _\bx_\bn_\bw_\bm operations;
+ should be some subset of csmln meaning control,
+ shift, meta, lock, and none.
+
+ LeftButton (l=value)
+ Sets the default left button function; should be one
+ of srmilzcp
+
+ MiddleButton (m=value)
+ Sets the default middle button function; should be
+ one of srmilzcp
+
+ RightButton (r=value)
+ Sets the default right button function; should be
+ one of srmilzcp
+
+ Geometry (={+-}xoff{+-}yoff)
+ Sets the location of the menu.
+
+FILES
+ /usr/new/lib/X/font directory of fonts
+
+ENVIRONMENT
+ DISPLAY - to get default host and
+ display number
+
+SEE ALSO
+ X(8C)
+
+AUTHOR
+ Paul Asente, Stanford University, using some algorithms ori-
+ ginally by Bob Scheifler, MIT Laboratory for Computer Sci-
+ ence
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 19 July 1985 5
+
+
+
--- /dev/null
+
+
+
+XPERFMON(1) UNIX Programmer's Manual XPERFMON(1)
+
+
+
+NAME
+ xperfmon - X window system Unix performance monitoring tool
+
+SYNOPSIS
+ xperfmon option [ option ] [ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by ]
+
+DESCRIPTION
+ This program allows you to monitor the performance of Unix
+ on a machine. The information will be plotted graphically
+ on a window. The possible options are user cpu time (user),
+ system cpu time (system), idle cpu time (idle), free memory
+ (free), disk transfers (disk), interrupts (interrupts),
+ input packets (input), output packets (output), collision
+ packets (collision). Any or all of these options can be
+ specified at once. By default, _\bx_\bp_\be_\br_\bf_\bm_\bo_\bn displays all of
+ these statistics.
+
+ -bd _\bc_\bo_\bl_\bo_\br
+ Specify the border color. On monochrome displays,
+ should be ``white'', ``black'', or ``gray''; gray is
+ the default.
+
+ -bg _\bc_\bo_\bl_\bo_\br
+ Specify the background color. On monochrome
+ displays, should be ``white'' or ``black''; black is
+ the default.
+
+ -bw _\bp_\bi_\bx_\be_\bl_\bs
+ Specify the width in pixels of the border around the
+ _\bx_\bp_\be_\br_\bf_\bm_\bo_\bn window. The default value is 3 pixels.
+
+ -fg _\bc_\bo_\bl_\bo_\br
+ Specify the graph color. On monochrome displays,
+ should be ``white'' or ``black''; white is the
+ default.
+
+ -fn _\bf_\bo_\bn_\bt_\bn_\ba_\bm_\be
+ The hostname will be displayed in the specified font
+ (if none is specified, this defaults to 6x10).
+
+ -hl _\bc_\bo_\bl_\bo_\br
+ Specify the hostname and scale line color; the
+ default is to make it the same as the graph color.
+
+ -rv Cause _\bx_\bp_\be_\br_\bf_\bm_\bo_\bn to produce all output in black-on-
+ white instead of white-on-black.
+
+ -fw Cause _\bx_\bp_\be_\br_\bf_\bm_\bo_\bn to produce all output in white-on-
+ black instead of black-on-white.
+
+ -scale _\bi_\bn_\bt_\be_\bg_\be_\br
+ Specify the minimum number of divisions on the graph
+
+
+
+Printed 9/15/87 2 July 1985 1
+
+
+
+
+
+
+XPERFMON(1) UNIX Programmer's Manual XPERFMON(1)
+
+
+
+ (default 1). _\bx_\bp_\be_\br_\bf_\bm_\bo_\bn is free to use more divisions
+ if the load gets too high to display, but it will
+ never use fewer divisions than this.
+
+ -u _\bs_\be_\bc_\bo_\bn_\bd_\bs
+ Set the update rate.
+
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by
+ Allows you to position the window on the screen.
+ See _\bX(_\b1) for a full description of geometry specifi-
+ cations.
+
+ [_\bh_\bo_\bs_\bt]:[_\bd_\bi_\bs_\bp_\bl_\ba_\by]
+ Normally, _\bx_\bp_\be_\br_\bf_\bm_\bo_\bn gets the host and display number
+ to use from the environment variable ``DISPLAY''.
+ Either or both can be specified with this option.
+ _\bh_\bo_\bs_\bt specifies which machine to create the _\bx_\bp_\be_\br_\bf_\bm_\bo_\bn
+ window on, and _\bd_\bi_\bs_\bp_\bl_\ba_\by specifies the display number.
+ For example, ``mit-grape-nehi:0'' creates an _\bx_\bp_\be_\br_\bf_\b-
+ _\bm_\bo_\bn on display 0 on machine mit-grape-nehi. Either
+ value can be defaulted by omission but `:' is neces-
+ sary to specify one or both.
+
+X DEFAULTS
+ Background
+ Set the background color.
+
+ Foreground
+ Set the graph color.
+
+ BodyFont
+ Set the hostname font.
+
+ BorderColor
+ Set the border color.
+
+ BorderWidth
+ Set the border width of the window.
+
+ Border Set the internal border of the window.
+
+ Highlight
+ Set the hostname and scale line color.
+
+ ReverseVideo
+ If ``on'', reverse the definition of foreground and
+ background color.
+
+ Scale Set the minimum scale.
+
+ Update Set the update interval.
+
+
+
+
+Printed 9/15/87 2 July 1985 2
+
+
+
+
+
+
+XPERFMON(1) UNIX Programmer's Manual XPERFMON(1)
+
+
+
+ENVIRONMENT
+ DISPLAY - to get the default host and display number.
+
+AUTHOR
+ Stephen Sutphen (University of Alberta).
+
+BUGS
+ This program is a CPU pig, getting the information out of
+ the kernel.
+
+SEE ALSO
+ X(8C)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 2 July 1985 3
+
+
+
--- /dev/null
+
+
+
+XPR(1) UNIX Programmer's Manual XPR(1)
+
+
+
+NAME
+ xpr - print X window dump
+
+SYNOPSIS
+ xpr [ -scale _\bs_\bc_\ba_\bl_\be ] [ -height _\bi_\bn_\bc_\bh_\be_\bs ] [ -width _\bi_\bn_\bc_\bh_\be_\bs ] [
+ -left _\bi_\bn_\bc_\bh_\be_\bs ] [ -top _\bi_\bn_\bc_\bh_\be_\bs ] [ -header _\bs_\bt_\br_\bi_\bn_\bg ] [ -trailer
+ _\bs_\bt_\br_\bi_\bn_\bg ] [ -landscape ] [ -portrait ] [ -output _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ] [
+ -append _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ] [ -noff ] [ -split _\bn ] [ -device _\bd_\be_\bv ] [
+ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ]
+
+DESCRIPTION
+ _\bX_\bp_\br takes as input an X window dump file produced by _\bx_\bw_\bd(1)
+ and formats it for output on the LN03 or LA100 printer. If
+ no file argument is given, the standard input is used. By
+ default, _\bx_\bp_\br prints the largest possible representation of
+ the window on the output page. Options allow the user to
+ add headers and trailers, specify margins, adjust the scale
+ and orientation, and append multiple window dumps to a sin-
+ gle output file. Output is to standard output unless -out-
+ put is specified.
+
+ Command Options
+
+
+ -scale _\bs_\bc_\ba_\bl_\be
+ Affects the size of the window on the page. The LN03
+ is able to translate each bit in a window pixel map
+ into a grid of a specified size. For example each bit
+ might translate into a 3x3 grid. This would be speci-
+ fied by -scale _\b3. By default a window is printed with
+ the largest scale that will fit onto the page for the
+ specified orientation.
+
+ -height _\bi_\bn_\bc_\bh_\be_\bs
+ Specifies the maximum height of the window on the page.
+
+ -width _\bi_\bn_\bc_\bh_\be_\bs
+ Specifies the maximum width of the window.
+
+ -left _\bi_\bn_\bc_\bh_\be_\bs
+ Specifies the left margin in inches. Fractions are
+ allowed. By default the window is centered in the
+ page.
+
+ -top _\bi_\bn_\bc_\bh_\be_\bs
+ Specifies the top margin for the picture in inches.
+ Fractions are allowed.
+
+ -header _\bh_\be_\ba_\bd_\be_\br
+ Specifies a header string to be printed above the win-
+ dow.
+
+
+
+
+Printed 9/15/87 27 August 1985 1
+
+
+
+
+
+
+XPR(1) UNIX Programmer's Manual XPR(1)
+
+
+
+ -trailer _\bt_\br_\ba_\bi_\bl_\be_\br
+ Specifies a trailer string to be printed below the win-
+ dow.
+
+ -landscape
+ Forces the window to printed in landscape mode. By
+ default a window is printed such that its longest side
+ follows the long side of the paper.
+
+ -portrait
+ Forces the window to be printed in portrait mode. By
+ default a window is printed such that its longest side
+ follows the long side of the paper.
+
+ -output _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ Specifies an output file name. If this option is not
+ specified, standard output is used.
+
+ -append _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ Specifies a filename previously produced by _\bx_\bp_\br to
+ which the window is to be appended.
+
+ -noff
+ When specified in conjunction with -append, the window
+ will appear on the same page as the previous window.
+
+ -split _\bn
+ This option allows the user to split a window onto
+ several pages. This might be necessary for very large
+ windows that would otherwise cause the printer to over-
+ load and print the page in an obscure manner.
+
+ -device _\bd_\be_\bv_\bi_\bc_\be
+ Specifies the device on which the file will be printed.
+ Currently only the LN03 and LA100 are supported.
+
+SEE ALSO
+ xwd(1), xdpr(1), xwud(1), X(1)
+
+LIMITATIONS
+ The current version of _\bx_\bp_\br can generally print out on the
+ LN03 most X windows that are not larger than two-thirds
+ of the screen. For example, it will be able to print out a
+ large Emacs window, but it will usually fail when trying
+ to print out the entire screen. The LN03 has memory limi-
+ tations that can cause it to incorrectly print very
+ large or complex windows. The two most common
+ errors encountered are ``band too complex'' and ``page
+ memory exceeded.'' In the first case, a window may have a
+ particular six pixel row that contains too many changes
+ (from black to white to black). This will cause the
+ printer to drop part of the line and possibly parts of the
+
+
+
+Printed 9/15/87 27 August 1985 2
+
+
+
+
+
+
+XPR(1) UNIX Programmer's Manual XPR(1)
+
+
+
+ rest of the page. The printer will flash the number `1' on
+ its front panel when this problem occurs. A possible solu-
+ tion to this problem is to increase the scale of the pic-
+ ture, or to split the picture onto two or more pages.
+ The second problem, ``page memory exceeded,'' will occur
+ if the picture contains too much black, or if the picture
+ contains complex half-tones such as the background
+ color of a display. When this problem occurs the
+ printer will automatically split the picture into two or
+ more pages. It may flash the number `5' on its from
+ panel. There is no easy solution to this problem. It
+ will probably be necessary to either cut and paste, or
+ rework to application to produce a less complex picture.
+
+ _\bX_\bp_\br provides some support for the LA100. However, there
+ are several limitations on its use: The picture will always
+ be printed in portrait mode (this may be changed in the
+ future;) there is no scaling; and the aspect ratio will
+ be slightly off.
+
+AUTHOR
+ Copyright 1985, Massachusetts Institute of Technology
+
+ Michael R. Gretzinger, MIT Project Athena
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 27 August 1985 3
+
+
+
--- /dev/null
+
+
+
+XREFRESH(1) UNIX Programmer's Manual XREFRESH(1)
+
+
+
+NAME
+ xrefresh - refresh all windows on the screen.
+
+SYNOPSIS
+ xrefresh [ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by ]
+
+DESCRIPTION
+ _\bX_\br_\be_\bf_\br_\be_\bs_\bh is a trivial X program to cause your screen to be
+ completely repainted. _\bX_\br_\be_\bf_\br_\be_\bs_\bh just throws a window over
+ the whole screen and unmaps it, causing refresh events to be
+ sent to all applications.
+
+ARGUMENT SUMMARY
+ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by This argument allow you to specify the
+ host and display number on which to display the window dump.
+ For example ``xrefresh orpheus:1'' would specify that the
+ dump will appear on display `1' on the machine `orpheus'.
+ By default, _\bx_\br_\be_\bf_\br_\be_\bs_\bh uses the host and display number stored
+ in the environment variable DISPLAY, and therefore this
+ argument is not normally specified.
+
+ENVIRONMENT
+ DISPLAY - To get default host and display number.
+
+SEE ALSO
+ X(1), uwm(1), X(8)
+
+AUTHOR
+ Copyright 1985, Massachusetts Institute of Technology.
+
+ Jim Gettys, Digital Equipment Corp., MIT Project Athena
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 October 25 1
+
+
+
--- /dev/null
+
+
+
+XSET(1) UNIX Programmer's Manual XSET(1)
+
+
+
+NAME
+ xset - X window system user setup program
+
+SYNOPSIS
+ xset option [ option ] [ _\bf_\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by ]
+
+DESCRIPTION
+ This program is used to set various user preference options
+ of the display. The c option controls key click, the l
+ option controls the lock key, the r option controls the auto
+ repeat, the b option controls bell volume, the m option con-
+ trols the mouse parameters, the p option controls pixel
+ color values, and the s and v options let you set the screen
+ saver parameters. Any of these can be preceded with a - to
+ disable the feature, or followed by on or off if you prefer.
+ The keyclick option can also be followed by an optional
+ digit between 1 and 8 to indicate volume. For example:
+ ``xset c on'' turns on keyclick; ``xset -r'' would turn off
+ autorepeat; ``xset b 5'' sets the bell volume.
+
+ The parameters for the mouse are ``acceleration'' and
+ ``threshold''. The acceleration of the mouse only takes
+ effect if the ``threshold'' is exceeded.
+
+ The parameters for a pixel are the color map entry number in
+ decimal, and a color specification. The root window colors
+ can be changed by altering entries 0 and 1. The map entry
+ must not be a read-only color, or an error will result.
+
+ The parameters for the screen saver function determines how
+ long the server must be inactive for screen saving to go on,
+ and the period to change the background pattern to avoid
+ burn in. The arguments are specified in minutes. Using the
+ v option sets the preference to blank the video (if the
+ hardware can do so) rather than display a background pat-
+ tern. Using the s option sets the preference to display a
+ pattern rather than blank the video.
+
+ These settings will be reset to default values when you log
+ out.
+
+ Note that not all X implementations are guaranteed to honor
+ all of these options.
+
+AUTHOR
+ Copyright (c) 1985, 1986 by Massachusetts Institute of Tech-
+ nology.
+ See _\bX(_\b1) for a full copyright notice.
+ Bob Scheifler, MIT Laboratory for Computer Science
+
+SEE ALSO
+ X(8C)
+
+
+
+Printed 9/15/87 15 November 1985 1
+
+
+
--- /dev/null
+
+
+
+XSHELL(1) UNIX Programmer's Manual XSHELL(1)
+
+
+
+NAME
+ xshell - X Window System, key/button command exec
+
+SYNOPSIS
+ xshell [ _\bo_\bp_\bt_\bi_\bo_\bn_\bs ] [ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by ] ...
+
+DESCRIPTION
+ _\bX_\bs_\bh_\be_\bl_\bl is a program for starting up X applications with a
+ single key or button stroke. It displays a scallop shell
+ icon in which button and key presses stand for different
+ commands. The user can bind a command string to any key or
+ button by inserting a line like the following in his or her
+
+ xshell.action.keyname: command to be exec'ed
+
+ Keynames are simply letters, numbers, and symbols as they
+ appear on the keyboard (e.g. a, $, 9), or one of the follow-
+ ing special names (taken from the X keyboard definitions):
+
+ KEYPAD0 FUNC1 E1
+ KEYPAD. FUNC2 E2
+ ENTER FUNC3 E3
+ KEYPAD1 FUNC4 E4
+ KEYPAD2 FUNC5 E5
+ KEYPAD3 FUNC6 E6
+ KEYPAD4 FUNC7 LEFTARROW
+ KEYPAD5 FUNC8 RIGHTARROW
+ KEYPAD6 FUNC9 DOWNARROW
+ KEYPAD, FUNC10 UPARROW
+ KEYPAD7 FUNC11 SHIFT
+ KEYPAD8 FUNC12 CONTROL
+ KEYPAD9 FUNC13 LOCK
+ KEYPAD- FUNC14 SYMBOL
+ PF1 FUNC15
+ PF2 FUNC16
+ PF3 FUNC17
+ PF4 FUNC18
+ LEFTBUTTON FUNC19
+ MIDDLEBUTTON FUNC29
+ RIGHTBUTTON
+
+
+ Thus, the following `.Xdefaults' definitions specify that
+ the Left Button will spawn a terminal window, the Middle
+ Button an editor, the Right Button a calculator, $ a Bourne
+ shell, and # a superuser shell:
+
+ xshell.action.LeftButton: xterm =80x65-0+0 -fn 6x10
+ xshell.action.MiddleButton: xted =80x65+0-0
+ xshell.action.RightButton: xterm =20x20-0-0 -fn 6x10 -e dc
+ xshell.action.$: xterm =80x65+0+0 -fn 6x10 -e sh
+ xshell.action.#: xterm =80x65+0+0 -fn 6x10 -e su
+
+
+
+Printed 9/15/87 31 October 1985 1
+
+
+
+
+
+
+XSHELL(1) UNIX Programmer's Manual XSHELL(1)
+
+
+
+ _\bX_\bs_\bh_\be_\bl_\bl breaks the command string up into words by removing
+ all white space (i.e. tabs and spaces) and uses the vfork()
+ and execvp() system calls to spawn off the command. A more
+ complicated parsing algorithm could easily be added, but the
+ current method is adequate (and fast and memory efficient).
+
+ One thing to keep in mind is that _\bx_\bs_\bh_\be_\bl_\bl is NOT a window
+ manager. It was written to make popping up frequently used
+ utilities as painless as possible (how many times have you
+ found that you need just 1 more window....). It might make
+ a nice addition to some of the more verbose window managers,
+ but it runs quite nicely as a separate program.
+
+
+ARGUMENTS
+ _\bX_\bs_\bh_\be_\bl_\bl is designed to be somewhat compatible with _\bx_\bc_\bl_\bo_\bc_\bk in
+ the arguments that it takes. However, _\bx_\bs_\bh_\be_\bl_\bl will allow you
+ to abbreviate its longer flags to any length you chose.
+ Thus, the -reverse flag can be spelled out, given as -rev,
+ or even just -r:
+
+ -fg _\bc_\bo_\bl_\bo_\br On color displays, determines the color of the
+ foreground.
+
+ -bg _\bc_\bo_\bl_\bo_\br On color displays, determines the color of the
+ background.
+
+ -bd _\bc_\bo_\bl_\bo_\br On color displays, determines the color of the
+ border.
+
+ -bw _\bp_\bi_\bx_\be_\bl_\bs
+ Specify the width in pixels of the border around
+ the _\bx_\bs_\bh_\be_\bl_\bl window.
+
+ -v[olume] _\bn
+ Volume for calls to _\bX_\bF_\be_\be_\bp, used when errors (such
+ as unbound key) are found.
+
+ -f[lash] _\bn
+ Number of times to flash the shell window to ack-
+ nowledge a button or key press.
+
+ -d[elay] _\bn
+ One-hundredths of a second to wait between flashs
+ (default is 5).
+
+ -r[everse]
+ Reverse video (swap foreground and background).
+
+ -q[uiet] Do not `feep' on errors (see volume).
+
+
+
+
+
+Printed 9/15/87 31 October 1985 2
+
+
+
+
+
+
+XSHELL(1) UNIX Programmer's Manual XSHELL(1)
+
+
+
+ -s[mall] Use a smaller (48x48) version of the shell icon.
+ The default icon is 96x96.
+
+ =_\bg_\be_\bo_\bm_\be_\bt_\br_\by By default _\bx_\bs_\bh_\be_\bl_\bl will create a window the size of
+ whatever icon you select; the standard X window
+ geometry argument will override this. See _\bX(_\b1)
+ for details.
+
+ _\bh_\bo_\bs_\bt:_\bd_\bi_\bs_\bp_\bl_\ba_\by
+ specifies the display on which to put the _\bx_\bs_\bh_\be_\bl_\bl
+ window. This overrides the DISPLAY environment
+ variable.
+
+
+X DEFAULTS
+ To make invoking _\bx_\bs_\bh_\be_\bl_\bl easier, each of the flags listed
+ above may be specified in the user's
+
+ Foreground
+ gives the foreground color.
+
+ Background
+ gives the background color.
+
+ Border gives the border color.
+
+ BorderWidth
+ gives the border width.
+
+ ReverseVideo
+ if "on", the shell icon should be white on black
+ instead of black on white.
+
+ Volume gives the volume to use in calls to XFeep().
+
+ Flash gives the number of times to flash the shell win-
+ dow to acknowledge key or button presses.
+
+ Delay gives hundredths of a second to wait in between
+ flashes.
+
+ Quiet prevents _\bx_\bs_\bh_\be_\bl_\bl from feeping at you when you mis-
+ type.
+
+ IconSize if "small", a halfsize (48x48) version of the
+ scallopshell is used.
+
+ WindowGeometry
+ gives the shell window size using standard X
+ =WxH+X+Y notation.
+
+
+
+
+
+Printed 9/15/87 31 October 1985 3
+
+
+
+
+
+
+XSHELL(1) UNIX Programmer's Manual XSHELL(1)
+
+
+
+ENVIRONMENT
+ DISPLAY To get the default host and display number.
+
+
+SEE ALSO
+ xwm(1), xnwm(1), X(1), execl(3), vfork(2)
+
+DIAGNOSTICS
+ If -quiet is not given on the command line or
+ ``xshell.Quiet: on'' does not appear in the user's ._\bX_\bd_\be_\b-
+ _\bf_\ba_\bu_\bl_\bt_\bs, _\bx_\bs_\bh_\be_\bl_\bl will `feep' if a key or button is pressed for
+ which there is no definition in the ._\bX_\bd_\be_\bf_\ba_\bu_\bl_\bt_\bs file.
+
+AUTHOR
+ Copyright 1985, Cognition Inc.
+
+ Jim Fulton (Cognition Inc.)
+
+BUGS
+ _\bX_\bs_\bh_\be_\bl_\bl uses the XGetDefault call to fetch the command string
+ for a given key. Thus, you cannot bind the colon (``:'')
+ character to a command.
+
+ A more `user-friendly' interface could include dialog boxes
+ that the user could pop up to type in a command directly so
+ that a full shell doesn't have to be started. Then again,
+ it is nice and compact now and if you really need to do that
+ more than once you should use a real shell.
+
+ This program along with _\bx_\bw_\bm(_\b1) and _\bx_\bn_\bw_\bm have been mostly
+ superceded by _\bu_\bw_\bm(_\b1).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Printed 9/15/87 31 October 1985 4
+
+
+