Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!tgr!root%bostonu.csnet@csnet-relay.arpa
From: root%bostonu.csnet@csnet-relay.arpa (BostonU SysMgr)
Newsgroups: net.unix-wizards
Subject: TERMCAPs extensions...
Message-ID: <9737@brl-tgr.ARPA>
Date: Thu, 4-Apr-85 19:56:14 EST
Article-I.D.: brl-tgr.9737
Posted: Thu Apr  4 19:56:14 1985
Date-Received: Mon, 8-Apr-85 00:17:12 EST
Sender: news@brl-tgr.ARPA
Lines: 25


We are starting to get systems that will emulate some terminal in
a window but are quite willing to create arbitrary height/width
which is nice.

The obvious problem is telling TERMCAP about all this. The 'hack'
solution is to 'printenv > foo', change foo, source foo (csh.)
This is a nuisance but works.

What occurs to me is to create environment variables HEIGHT and
WIDTH and thus it's a simple matter of a 'setenv' to change things
which is pretty easy to get the workstation to send or to type in.
The tgetnum() routine could be changed so if it is asked for co or li
it can check these first (or maybe a new cap added like a bool CV,LV
for column variable, line variable or whatever though the first is
more transparent.)

This is all far too trivial to bother this list about, my real question
is:

	This must have been solved several times, how? Standards?

		-Barry Shein, Boston University

P.S. Yes I know TOPS-20 has this (I always get those kind of answers!)