Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site baylor.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!rochester!rocksanne!sunybcs!kitty!baylor!peter
From: peter@baylor.UUCP (Peter da Silva)
Newsgroups: net.sources
Subject: Re: Re:  Trouble with visual strek
Message-ID: <601@baylor.UUCP>
Date: Thu, 3-Oct-85 16:42:45 EDT
Article-I.D.: baylor.601
Posted: Thu Oct  3 16:42:45 1985
Date-Received: Sun, 6-Oct-85 04:25:02 EDT
References: <1632@brl-tgr.ARPA> <110@birtch.UUCP>
Organization: The Power Elite, Houston, TX
Lines: 17

> > there is definitly a problem and it appears terminal type dependent.
> > the vtrek works on an adm3a with Unix4.2bsd on an 11/780 but has alot of
> > ones on the screen with an zenith or heathkit 19 terminal
> 
> I have found that vt52 terminals on our Pyramid 90x ( 4.2 & V5, in 
> 4.2 BSD univerce) work just fine. vt100 on the other hand did not.
> I traced the problem to TERMCAP : vt100 entry contains the length of
> character sequence in front of  "cm", "cl" and some other sequences.

That's not quite what they are, and it's probably not a good idea to zap them.
They are the delay times (in seconds/10) for the terminal... the VT100 can
easily confused on a fast line if you leave these out. The solution is
to use tputs() instead of printf() (or whatever) to display these strings.
-- 
	Peter (Made in Australia) da Silva
		UUCP: ...!shell!neuro1!{hyd-ptd,baylor,datafac}!peter
		MCI: PDASILVA; CIS: 70216,1076


Brought to you by Super Global Mega Corp .com