Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!enea!erix!per
From: per@erix.UUCP (Per Hedeland)
Newsgroups: comp.unix.wizards
Subject: Re: Two process communication programs
Message-ID: <1352@erix.UUCP>
Date: Tue, 23-Jun-87 09:03:13 EDT
Article-I.D.: erix.1352
Posted: Tue Jun 23 09:03:13 1987
Date-Received: Sat, 27-Jun-87 06:57:48 EDT
References: <651@vixie.UUCP> <140@fesk.UUCP> <655@vixie.UUCP>
Reply-To: per@erix.UUCP (Per Hedeland)
Organization: Ericsson Telecom, Stockholm, Sweden
Lines: 42

In article <655@vixie.UUCP> paul@vixie.UUCP (Paul Vixie Esq) writes:
>In article <140@fesk.UUCP> sverre@fesk.UUCP (Sverre Froyen) writes:
>#in article <651@vixie.UUCP>, paul@vixie.UUCP (Paul Vixie Esq) says:
>#> ...  I was sufficiently disgusted with the ^A and ^P
>#> behaviour that I hacked tip to have two new variables:
>#Isn't this an overkill. A .tiprc file containing the two lines
>#	force=
>#	raisechar=
>#has the same effect.
>
>Hmmm, I hadn't thought of that.

Hmm-hmm, I *had*, only trouble is, it doesn't work... As the loud screaming
from emacs users will make you realize, this will set both of 'force' and
'raisechar' to be ascii NUL! And (of course :-( ) 'raisechar' takes precedence,
so you can't even "force" it.

This is due to the fact that these variables are of the "character" type,
and there isn't really a general way to unset character variables (the above 
would have worked for string variables).

However, there is a workaround (pronounced "kludge"): Using the \ escape, it
is possible to set a character variable to a value with bit 7 on, e.g.
	force=\377
and since bit 7 is stripped on tip's input, it will be effectively disabled.
'~[set] all' will incorrectly tell you that ^? (aka DEL) is the current
value of these variables, though (just as it will incorrectly tell you that
they haven't got one if you try the proposal above...).

> I can see an advantage to having it in the /etc/remote
>file, since I can put :nf:nr: into the entry that all the other entries
>:tc=: to, and have ^A/^P totally gone from my TIP.

Among the many other things that remote(5) doesn't mention, is the fact
that both 'force' and 'raisechar' may be set from /etc/remote (at least in
4.3BSD - am I violating our license by revealing it...?). The "capability" 
names are, by pure coincidence, equal to the "abbreviations" listed in tip(1); 
thus you can put :fo=\377:rc=\377: there to achieve this effect.

--Per Hedeland
per@erix.se  or  {mcvax,seismo}!erix!per

PS. I *do* like tip, all the same...