Return to xinit.man CVS log

Up to [Research Unix] / researchv9 / X11 / src / X.V11R1 / clients / xinit

Annotation of researchv9/X11/src/X.V11R1/clients/xinit/xinit.man, revision 1.1

1.1     ! root        1: .TH XINIT 1 "25 January 1986" "X Version 10"
        !             2: .SH NAME
        !             3: xinit - X window system initializer
        !             4: .SH SYNOPSIS
        !             5: .B xinit
        !             6: [[client] options] [-- [server] [display] options]
        !             7: .SH DESCRIPTION
        !             8: .I Xinit
        !             9: is intended to be used when the X window system server is not run automatically
        !            10: from \fIinit(8)\fP,
        !            11: and the window system must be started from a shell running on
        !            12: the display.  This might be true, for example, if a normal login is run in a
        !            13: glass-tty emulator on a workstation console, so that different window systems
        !            14: can easily be run on the display at different times.
        !            15: .PP
        !            16: \fIXinit\fP starts up the server and a single client application,
        !            17: which is typically
        !            18: \fIxterm(1)\fP.
        !            19: When the client eventually terminates, \fIxinit\fP automatically kills off
        !            20: the server and then itself terminates.
        !            21: .PP
        !            22: By default, 
        !            23: \fIxinit\fP expects the server to exist in an executable named ``X'' in
        !            24: the search path, 
        !            25: and for \fIxterm(1)\fP to also exist in the search path.  
        !            26: It starts
        !            27: up the X server on display 0, and then starts up
        !            28: .br
        !            29:        xterm =+1+1 -n login unix:0
        !            30: .br
        !            31: .PP
        !            32: A different client and/or server can be specified in the command line, and
        !            33: command line options can be passed to both the server and the client.  The
        !            34: client and its options come first in the command line.  The server and its
        !            35: options must be preceded by ``--''.
        !            36: If the first argument to xinit begins with `/' or a letter, it is taken to
        !            37: be the client program to use instead of xterm, and none of the default xterm
        !            38: options are used.  Otherwise, the first and subsequent arguments are
        !            39: simply appended as further options to the default \fIxterm\fP command line.
        !            40: .PP
        !            41: Following the ``--'' argument,
        !            42: if the next argument begins with `/' or a letter,
        !            43: it is taken to be the server program to use instead of ``X''.  If the next
        !            44: argument begins with a digit, it is taken to be the display number; otherwise
        !            45: display 0 is assumed.  The remaining arguments are added as options to the
        !            46: server command line.
        !            47: .PP
        !            48: Examples:
        !            49: .sp
        !            50: xinit =80x65+10+10 -fn 8x13 -j -fg white -bg navy
        !            51: .br
        !            52: xinit -e widgets -- Xsun -l -c
        !            53: .br
        !            54: xinit rsh fasthost cpupig workstation:1 -- 1 -a 2 -t 5
        !            55: .br
        !            56: .SH AUTHOR
        !            57: Copyright (c) 1986 by Massachusetts Institute of Technology.
        !            58: .br
        !            59: See \fIX(1)\fP for a complete copyright notice.
        !            60: .br
        !            61: Bob Scheifler, MIT Laboratory for Computer Science
        !            62: .SH "SEE ALSO"
        !            63: X(8C), xterm(1)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.