Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.questions
Subject: Re: Termcap question
Keywords: termcap
Message-ID: <12264@smoke.BRL.MIL>
Date: 2 Mar 90 03:21:38 GMT
References: <5658@star.cs.vu.nl> <671@mwtech.UUCP> <5708@star.cs.vu.nl>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <5708@star.cs.vu.nl> gpvos@cs.vu.nl (Vos G P) writes:
>This introduces another problem, though. Now i can't get a \0 in my strings!
>Can someone help me with that? As no high bits are stripped, \200 gives me
>a neat \200, instead of the \0 the man pages say.

I hope \200 will serve your terminal's needs, because you cannot embed
a constant \000 in termcap strings; they're handled by programs as C
null-terminated strings and thus cannot contain a 0-valued byte.  A 0
byte can be output via termcap/libtermlib only as the result of
parameter substitution (or, of course, as a padding character).

I'm curious as to the kind of terminal you have that requires a 0 byte
for some non-padding function.  I've never encountered this myself..