'\"macro stdmacro
.if n .pH g1.olinit @(#)olinit	40.3 of 1/9/90
.nr X
.if \nX=0 .ds x} OLINIT 1 "12/1/89" "OPEN LOOK 2.0" "\&"
.if \nX=1 .ds x} OLINIT 1 "12/1/89" "OPEN LOOK 2.0"
.if \nX=2 .ds x} OLINIT 1 "" "\&"
.if \nX=3 .ds x} OLINIT "" "" "\&"
.TH \*(x}
.tr ~
.IX \f2olinit\f1 command
.IX applications supported, olinit
.nr % 1
.SH NAME
olinit - initialize the OPEN LOOK Graphical User Interface
.SH SYNOPSIS
.B olinit
[[client] options] [-- [server] [display] options]
.SH DESCRIPTION
The
\f2olinit\f1 program
is similar to the original X Window System \f2xinit\f1
program, but is described here in detail to outline the
difference. Aside from naming conventions, the major
difference is that the default primary client is the OPEN LOOK
workspace manager instead of \f2xterm.\f1
.PP
The
\f2olinit\f1 program
is used to start the X Window System server, a primary client
program (the OPEN LOOK workspace manager), and (optionally
through an \f2.olinitrc\f1 file) secondary clients (e.g.,
window manager or \f2xterm\f1). When the primary client exits, 
\f2olinit\f1
will kill the X server and then terminate. If the X server
exits, 
\f2olinit\f1
will kill the primary client and the secondary clients
and then terminate.
.PP
Unless otherwise specified on the command line,
\f2olinit\f1
assumes that there are programs called \f2X\f1 and 
\f2olwsm\f1 in the
current search path. It starts the server on display 0 and
then runs \f2olwsm\f1.
.P
An alternate primary client and/or server may be specified on
the command line. The desired client program and its arguments
should be given as the first command line arguments to 
\f2olinit\f1.
To specify a particular server command line, append a double
dash (--) to the 
\f2olinit\f1
command line (after any client and arguments) followed by the
desired server command.
.PP
Otherwise, they are
treated as arguments to be appended to their respective
startup lines. This makes it possible to add arguments (for
example, foreground and background colors) without having to
retype the whole command line.
.PP
If an explicit server name is not given and the first argument
following the double dash (--) is a digit, 
the
\f2olinit\f1 program
will use that number as the display number instead of zero.
All remaining arguments are appended to the server command
line.
.PP
\f2olinit\f1 also creates files 
called \f2.oliniterr\f1 and \f2.olinitout\fP
and places them in the user's home
directory. All errors and warnings are put in 
the \f2.oliniterr\fP
file. Output to \f2stdout\fP is written out to 
the \f2.olinitout\fP
file.
.PP
An \f2.olinitrc\f1 file can be used to start secondary
clients if \f2olwsm\f1 is the primary client. 
Since it is the responsibility of \f2olwsm\f1 to execute 
the \f2.olinitrc\f1 file, the contents of \f2.olinitrc\f1 will
be ignored if an application other than \f2olwsm\f1 is the
primary client for \f2olinit\f1. \f2olwsm\f1 looks for this
file in the user's home directory.
The format of this file is typically:
.PP
.TP 30
.B client_a &
.TP 30
.B client_b &
.TP 30
.B \...
.PP
If you run \f2.olinit\fP with any client other than \f2olwsm\fP as the
primary client, the \f2.olinitrc\fP file will not be executed.
.PP
.SH FILES
$HOME/.olinitrc
.br
$HOME/.oliniterr
.br
$HOME/.olinitout
.PP
.SH NOTE
\f2~.olinout\fP can only be used for starting the server and
clients on the same machine. Using \f2olinit\fP with remote
servers is not supported in this release.
.PP
\f2olinit\fP can be used to change the screen resolution to
one of three different resolutions with
the following command:
.PP
\f3olinit -- x -lines [600] [480] [400]\fP
