Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!hc!beta!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: termcap question
Message-ID: <5944@brl-smoke.ARPA>
Date: Thu, 4-Jun-87 00:13:38 EDT
Article-I.D.: brl-smok.5944
Posted: Thu Jun  4 00:13:38 1987
Date-Received: Sat, 6-Jun-87 05:37:07 EDT
References: <84@decvax.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <84@decvax.UUCP> tim@decvax.UUCP (Tim Burke) writes:
>Why does the 43BSD documentation state that only certain strings in the
>/etc/termcap file are able to use padding?

Basically, because it's traditionally been that way in the termcap(5)
manual entry.  As you observed, tputs() can handle padding for any
possible string capability.  Think of the capabilities flagged in
termcap(5) as accepting padding as simply a guide to the ones for
which padding makes most sense and is commonly needed.

I suppose this should be clarified in the next edition.

	- D A Gwyn, 4.3BSD termcap(5) editor