Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!tektronix!orca!tekecs!doghouse!snoopy
From: snoopy@doghouse.UUCP
Newsgroups: comp.sources.d
Subject: Re: when using termcap, get it right!
Message-ID: <8601@tekecs.TEK.COM>
Date: Thu, 28-May-87 13:21:08 EDT
Article-I.D.: tekecs.8601
Posted: Thu May 28 13:21:08 1987
Date-Received: Sat, 30-May-87 06:05:18 EDT
References: <1149@carthage.swatsun.UUCP>
Sender: nobody@tekecs.TEK.COM
Reply-To: snoopy@doghouse.gwd.tek.com (Snoopy)
Organization: The Daisy Hill Puppy Farm
Lines: 22
Keywords: termcap, curses

In article <1149@carthage.swatsun.UUCP> schwartz@swatsun (Scott Schwartz) writes:

>	This is a complaint, I guess.  At Swarthmore we have lots of Adds
>Viewpoint terminals.  On these beasties the escape sequences to enter
>standout mode, underline mode, normal mode, etc all take up one space
>on the screen (gaak).  The problem is that lots of programs that go 
>to lots of trouble to figure out what the termcap entries for these
>things are never bother to check the width of the entries as printed.
>So microEmacs (all versions that I know of, up to 3.8f), for example, 
>prints like this on a viewpoint:

>	n o s p a c e s

Am I missing something here, or should these termcap entries include
a backspace to return the curser to where it belongs?

Why screw up a bunch of code to get around brain-damaged hardware
if it can be fixed in the termcap entry?

Snoopy
tektronix!doghouse.gwd!snoopy
snoopy@doghouse.gwd.tek.com