Initial commit

1 files changed, 42 insertions, 0 deletions

diff --git a/vendor/x11iraf/xgterm/Tests b/vendor/x11iraf/xgterm/Tests
new file mode 100644
index 00000000..f270e203
--- /dev/null
+++ b/vendor/x11iraf/xgterm/Tests
@@ -0,0 +1,42 @@
+Tests for xgterm:
+
+If system supports window size (i.e., some combination of SIGWINCH,
+TIOCSSIZE, TIOCSWINSZ), start a full-screen program (e.g., Emacs,
+Jove, vi) and resize the xgterm window.  The program must immediately
+update its screen image for the new size.
+
+If compiled with -DUTMP, starting a new xgterm should create a new utmp
+entry.  ("who" will show this info.)  Exiting xgterm should remove the
+entry.  Killing the xgterm window (or other unnatural exit) should also
+remove the entry.  When should entries be made in the wtmp file?
+
+Process group stuff should be correct.
+
+Should work without access to /dev/tty, say started from an xdm
+started from a boot-time script.
+
+If "xgterm -help" offers the -C option, it should work.
+
+echo "test" > /dev/tty
+
+vi with lines that wrap.
+
+Exec'ing things other than shells.
+
+Another thing that has caused problems in the past is process groups,
+especially w.r.t. signal propagation to the child.
+
+Popup menu signals: running only a shell, click on "Send INT Signal."
+Do you get a new prompt from the shell?  (Same as typing ^C at it.)
+
+Should scroll *fast* with jumpScroll enabled.
+
+While a mouse button is down tracing out a selection, output to the
+screen should be suspended.
+
+Selections more than one screen long.
+
+start xgterm running only Tek widget: "xgterm -t"
+
+
+Please add to this list if you find xgterm failing in some way.