Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!tness1!sugar!ficc!peter
From: peter@ficc.UUCP (Peter da Silva)
Newsgroups: comp.unix.xenix
Subject: Re: OOPS and Foxbase
Keywords: Foxbase, tty, filters, OOPS
Message-ID: <1341@ficc.UUCP>
Date: 23 Aug 88 13:52:59 GMT
References: <6808@well.UUCP> <269@hawkmoon.MN.ORG>
Distribution: na
Organization: SCADA
Lines: 22

In article <269@hawkmoon.MN.ORG>, det@hawkmoon.MN.ORG (Derek E. Terveer) writes:
> Apparently, the OOPS is an exclaimation of suprise by curses when it
> encounters things in the termcap file it doesn't understand.  This
> doesn't seem to be a documented feature.

Actually it's a documented error message from termlib which is what curses uses
to do the actual termcap stuff on Version 7 based curses.

It is caused by tgoto when it is given an invalid :cm: string, either because
tgetstr didn't find the string (perhaps your .profiles aren't set up right
for dialups... try "TERM=xxx; export TERM" or "setenv TERM xxx"), or when the
string contains unexpected escape sequences (your termlib might be more
advanced than foxbase's: %p is not a standard termcap function, it's borrowed
from terminfo).

tgoto is called for all parameterised sequences, which explains why multiline
deletes could cause problems. See if you can find an older termcap definition,
say from a V7 or BSD manual, and try cutting anything that doesn't show up in
that.
-- 
Peter da Silva  `-_-'  Ferranti International Controls Corporation.
"Have you hugged  U  your wolf today?"     sugar.uu.net!ficc!peter.