🚀 go-pugleaf

In article <544@sequent.cs.qmc.ac.uk> sheridan@nss.cs.ucl.ac.uk writes:
>or_perhaps_Reply_to: flash@cs.qmc.ac.uk

>Be careful, uw on startup re-defines your TERM variable, but not TERMCAP.
>This is what caught me.

This is an oversight on the part of the author.  Uw DOES define your
TERMCAP variable on startup, if and only if you are using adm31
emulation.  This is because John Bruner uses only the adm31 emulation
himself, I think.  The problem is easily fixed if you have access to
the uw sources on your host, and can persuade your system
administrator to let you fix them.  (Even better if you ARE the
sysop!)

The TERMCAP strings are defined in server/uw_tty.c, and all you have
to do is fill in the missing ones.  It has been a long time since I
did this, but I have a uw server here which fills in environment
TERMCAP entries for adm31, ansi, vt52, and tek!  For added zest, a few
lines of code added to uw_fork.c lets you use uwtool to put up a new
window of a different type and with the correct TERMCAP defined.  I
sent John Bruner mail on this point a few times, but got no reply, for
whatever reasons.  I conclude that either he is too busy, doesn't
perceive this as a problem, or simply didn't get the mail.

Since the program contains a copyright notice, I wouldn't feel right
posting diffs, but any competent C programmer should be able to fix
this once he finds the line defining the TERMCAP string.

Earle Horton


Earle R. Horton.  H.B. 8000, Dartmouth College, Hanover, NH 03755