1Tests for xterm:
2
3If system supports window size (i.e., some combination of SIGWINCH,
4TIOCSSIZE, TIOCSWINSZ), start a full-screen program (e.g., Emacs,
5Jove, vi) and resize the xterm window.  The program must immediately
6update its screen image for the new size.
7
8If compiled with -DUTMP, starting a new xterm should create a new utmp
9entry.  ("who" will show this info.)  Exiting xterm should remove the
10entry.  Killing the xterm window (or other unnatural exit) should also
11remove the entry.  When should entries be made in the wtmp file?
12
13Process group stuff should be correct.
14
15Should work without access to /dev/tty, say started from an xdm
16started from a boot-time script.
17
18If "xterm -help" offers the -C option, it should work.
19
20echo "test" > /dev/tty
21
22vi with lines that wrap.
23
24Exec'ing things other than shells.
25
26Another thing that has caused problems in the past is process groups,
27especially w.r.t. signal propagation to the child.
28
29Popup menu signals: running only a shell, click on "Send INT Signal."
30Do you get a new prompt from the shell?  (Same as typing ^C at it.)
31
32Should scroll *fast* with jumpScroll enabled.
33
34While a mouse button is down tracing out a selection, output to the
35screen should be suspended.
36
37Selections more than one screen long.
38
39start xterm running only Tek widget: "xterm -t"
40
41
42Please add to this list if you find xterm failing in some way.
43