xref: /original-bsd/usr.bin/window/README (revision 07711933)
1/*-
2 * Copyright (c) 1990, 1993
3 *	The Regents of the University of California.  All rights reserved.
4 *
5 * This code is derived from software contributed to Berkeley by
6 *  Edward Wang at The University of California, Berkeley.
7 *
8 * %sccs.include.redist.c%
9 *
10 *	@(#)README	8.1 (Berkeley) 06/06/93
11 */
12
13Compilation notes:
14
15     Compiler options:
16
17	BYTE_ORDER (used only in ww.h)
18		It should already be defined in machine/endian.h.
19		The code knows about BIG_ENDIAN, LITTLE_ENDIAN, and PDP_ENDIAN.
20		It only cares about byte order in words, so PDP_ENDIAN
21		is the same as LITTLE_ENDIAN.
22	OLD_TTY
23		If you don't have Posix termios, then define this.
24	VMIN_BUG
25		Even if you have Posix termios, define this if the MIN and TIME
26		feature in noncanonical mode doesn't work correctly.
27
28     Ok, there's another one, STR_DEBUG.  It turns on consistency checks
29     in the string allocator.  It's been left on since performace doesn't
30     seem to suffer.  There's an abort() somewhere when an inconsistency
31     is found.  It hasn't happened in years.
32
33     The file local.h contains locally tunable constants.
34
35     The makefile used to be updated with mkmf; it has been changed
36at various times to use cpp -M and, currently, mkdep.  The only library
37it needs is termcap.
38
39     Window, as is, only runs on 4.3 (or later) machines.
40
41     On 4.2 machines, at least these modifications must be done:
42
43	delete uses of window size ioctls: TIOCGWINSZ, TIOCSWINSZ,
44		struct winsize
45	add to ww.h
46		typedef int fd_set;
47		#define FD_ZERO(s) (*(s) = 0)
48		#define FD_SET(b, s) (*(s) |= 1 << (b))
49		#define FD_ISSET(b, s) (*(s) & 1 << (b))
50	add to ww.h
51		#define sigmask(s) (1 << (s) - 1)
52
53
54A few notes about the internals:
55
56     The window package.  Windows are opened by calling wwopen().
57Wwwrite() is the primitive for writing to windows.  Wwputc(), wwputs(),
58and wwprintf() are also supported.  Some of the outputs to windows are
59delayed.  Wwupdate() updates the terminal to match the internal screen
60buffer.  Wwspawn() spawns a child process on the other end of a window,
61with its environment tailored to the window.  Visible windows are
62doubly linked in the order of their overlap.  Wwadd() inserts a window
63into the list at a given place.  Wwdelete() deletes it.  Windows not in
64the list are not visible, though wwwrite() still works.  Window was
65written before the days of X and Sunview, so some of the terminology
66is not standard.
67
68     Most functions return -1 on error.  Wwopen() returns the null
69pointer.  An error number is saved in wwerrno.  Wwerror() returns an
70error string based on wwerrno suitable for printing.
71
72     The terminal drivers perform all output to the physical terminal,
73including special functions like character and line insertion and
74deletion.  The window package keeps a list of known terminals.  At
75initialization time, the terminal type is matched against the list to
76find the right terminal driver to use.  The last driver, the generic
77driver, matches all terminals and uses the termcap database.  The
78interface between the window package the terminal driver is the `tt'
79structure.  It contains pointers to functions to perform special
80functions and terminal output, as well as flags about the
81characteristics of the terminal.  Most of these ideas are borrowed
82from the Maryland window package, which in turn is based on Goslin's
83Emacs.
84
85     The IO system is semi-synchronous.  Terminal input is signal
86driven, and everything else is done synchronously with a single
87select().  It is roughly event-driven, though not in a clean way.
88
89     Normally, in both conversation mode and command mode, window
90sleeps in a select() in wwiomux() waiting for data from the
91pseudo-terminals.  At the same time, terminal input causes SIGIO which
92is caught by wwrint().  The select() returns when at least one of the
93pseudo-terminals becomes ready for reading.
94
95     Wwrint() is the interrupt handler for tty input.  It reads input
96into a linear buffer accessed through four pointers:
97
98	+-------+--------------+----------------+
99	| empty |    data      |   empty	|
100	+-------+--------------+----------------+
101	^	^		^		 ^
102	|	|		|		 |
103       wwib    wwibp	       wwibq		wwibe
104
105Wwrint() appends characters at the end and increments wwibq (*wwibq++
106= c), and characters are taken off the buffer at wwibp using the
107wwgetc() and wwpeekc() macros.  As is the convention in C, wwibq
108and wwibe point to one position beyond the end.  In addition,
109wwrint() will do a longjmp(wwjmpbuf) if wwsetjmp is true.  This is
110used by wwiomux() to interrupt the select() which would otherwise
111resume after the interrupt.  (Actually, I hear this is not true,
112but the longjmp feature is used to avoid a race condition as well.
113Anyway, it means I didn't have to depend on a feature in a
114daily-changing kernel, but that's another story.) The macro
115wwinterrupt() returns true if the input buffer is non-empty.
116Wwupdate(), wwwrite(), and wwiomux() check this condition and will
117return at the first convenient opportunity when it becomes true.
118In the case of wwwrite(), the flag ww_nointr in the window structure
119overrides this.  This feature allows the user to interrupt lengthy
120outputs safely.  The structure of the input buffer is designed to
121avoid race conditions without blocking interrupts.
122
123     Actually, wwsetjmp and wwinterrupt() are part of a software
124interrupt scheme used by the two interrupt catchers wwrint() and
125wwchild().  Asserting the interrupt lets the synchronous parts of
126the program know that there's an interesting asynchronous condition
127(i.e., got a keyboard character, or a child process died) that they
128might want to process before anything else.  The synchronous routines
129can check for this condition with wwinterrupt() or by arranging
130that a longjmp() be done.
131
132     Wwiomux() copies pseudo-terminal output into their corresponding
133windows.  Without anything to do, it blocks in a select(), waiting for
134read ready on pseudo-terminals.  Reads are done into per-window buffers
135in the window structures.  When there is at least one buffer non-empty,
136wwiomux() finds the top most of these windows and writes it using
137wwwrite().  Then the process is repeated.  A non-blocking select() is
138done after a wwwrite() to pick up any output that may have come in
139during the write, which may take a long time.  Specifically, we use
140this to stop output or flush buffer when a pseudo-terminal tells us to
141(we use pty packet mode).  The select() blocks only when all of the
142windows' buffers are empty.  A wwupdate() is done prior to this, which
143is the only time the screen is guaranteed to be completely up to date.
144Wwiomux() loops until wwinterrupt() becomes true.
145
146     The top level routine for all this is mloop().  In conversation
147mode, it simply calls wwiomux(), which only returns when input is
148available.  The input buffer is then written to the pseudo-terminal of
149the current window.  If the escape character is found in the input,
150command mode is entered.  Otherwise, the process is repeated.  In
151command mode, control is transferred to docmd() which returns only when
152conversation mode is reentered.  Docmd() and other command processing
153routines typically wait for input in a loop:
154
155	while (wwpeekc() < 0)
156		wwiomux();
157
158When the loop terminates, wwgetc() is used to read the input buffer.
159
160     Output to the physical terminal is handled by the lowest level
161routines of the window package, in the files ttoutput.c and tt.h.  The
162standard IO package is not used, to get better control over buffering
163and to use non-blocking reads in wwrint().  The buffer size is set to
164approximately one second of output time, based on the baudrate.
165
166     The result of all this complexity is faster response time,
167especially in output stopping and flushing.  Wwwrite() checks
168wwinterrupt() after every line.  It also calls wwupdate() for each line
169it writes.  The output buffer is limited to one second of output time.
170Thus, there is usually only a delay of one to two lines plus one second
171after a ^C or ^S.  Also, commands that produce lengthy output can be
172aborted without actually showing all of it on the terminal.  (Try the
173'?' command followed by escape immediately.)
174