karl@ucbvax.Berkeley.EDU (10/23/85)
From: ucdavis!lll-crg!seismo!rlgvax!vrdxhq!karl@ucbvax.Berkeley.EDU (Karl Nyberg)
From the /etc/termcap entry for tvi950
:ct=\E3:st=\E1:cr=^M:do=^J:nl=^J:bl=^G:\
:is=\EDF\EC\Ed\EG0\Eg\Er\EO\E\047\E(\E%\Ew\EX\Ee ^O\
\El\E016\E004\Ex0\200\200\Ex1\200\200\Ex2\200\200\
\Ex3\200\200\Ex4\r\200\Ef\r:\
:al=\EE:am:le=^H:bs:bt=\EI:cd=\Ey:ce=\Et:cl=\E*:cm=\E=%+ %+ :\
:co#80:dc=\EW:dl=\ER:do=^V:ei=\Er:ho=^^:im=\Eq:k0=^A0\r:\
1) There are two entries for the capability "do". Does this mean that
either capability can be used? (The C termlib routines select the
first entry.)
2) Tgetstr ("is") returns a string that has embedded tabs between the
...^O and the \El... and between the ...\Ex2\200\200 and the \Ex3...
that, although they seem to be innocuous enough when displayed to the
screen in tset(1), don't appear to be properly included in the
capability. I presume that ALL string capabilities that extend over a
single line have this same "feature"? Should not the whitespace at
the beginning of the line be removed as well as the escaped newline?
--
-- Karl
--
DDN: nyberg@eclb, nyberg@utexas-20, Nyberg@mit-multics
UUCP: ...!{rlgvax, seismo, trwatf, umcp-cs, verdix}!vrdxhq!karl