Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!milton!mrc
From: MRC@CAC.Washington.EDU (Mark Crispin)
Newsgroups: comp.sys.next
Subject: Re: characters preempted by tip
Message-ID: <1991Jun2.230253.6651@milton.u.washington.edu>
Date: 2 Jun 91 23:02:53 GMT
References: <15793@adobe.UUCP> <515@heaven.woodside.ca.us>
Sender: mrc@milton.u.washington.edu (Mark Crispin)
Organization: University of Washington, Seattle
Lines: 24

In article <515@heaven.woodside.ca.us> glenn@heaven.woodside.ca.us (Glenn Reid) writes:
>Ed Taft writes
>> I suppose I can set the raise and force functions to be characters I rarely
>> use. But I would prefer to turn them off altogether. Does anyone know how to
>> accomplish this?
>You can also set these as defaults in your .tiprc file as follows:
>raisechar=
>force=

Ed said he wanted to turn them off altogether.  The .tiprc file trick
does *NOT* turn them off.  It sets those bloody characters to NUL.

I am rapidly becoming fed up with tip.  Not only does it have these
two bogons, it also seems to be impossible to turn off XON/XOFF
handling or get 8-bit transparency.  At least if it is possible, it's
unknown to me and our local UNIX gurus.  The alleged tip function to
turn off parity handling is equivalent to space parity.

Kermit works better, but it has its own annoyances.  I'm getting
tempted to write a new program, although I feel a bit reluctant to
inflict Yet Another Telnet-to-TTY program on the world.  Has anyone
written the ultimate dial program?

-- DoD#105