EOF Marker

[Brian K. White]

Bob Stockler wrote:
> I moved from SCO OSR 5.0.5 to OSR 5.0.6, using filePro
> v5.0.07D4 with the scoansi termcap.
>
> Since filePro v4.8.09K2D4 the scoansi termcap I've used
> has GZ=~ which has always given me a small (about half
> the height of the cursor) reverse-video square as the
> End of Field Marker.
>
> Now, on OSR 5.0.6, it gives me the literal tilde - ~ -
> assigned to GZ in the termcap.
>
> I don't want to "mkdev scoansi" and use the in-kernel
> just to get this behavior back, and I've found some
> substitutes that I line better than the tilde, but if
> someone knows how I could get my little black box back
> I'd like to know.
>
> Bob


The reason the ~ used to display as an upper-ascii character has to do with
the fact that there are more than one way to skin the same cat in termcap.

Way 1) You can set GS and GE to nothing so that you don't try to switch into
any alternate character set when drawing a G* character. And then send the
actual 8-bit high-ascii value for the character you want by setting GZ=\376

Way 2) You set GS and GE to the ansi codes for switching into and back out
of an alternate character set, And then define the G* fields to low-ascii
7-bit values that only display as special characters while in that alternate
character set. This is the case when GZ=~

first thing I'd try in your case since ~ is looking like an untranslated ~
is change GZ to  GZ=\376 in fp/termcap

In your case what I'd do is:
put "mapchan -n" in /etc/profile
and put GZ=\376 in fp/termcap
and verify that TERM=ansi instead of say, "scoansi" which I've seen recent
version do out of the box.
I actually put this in /etc/profile also to catch that and make TERM get set
to "ansi" if it starts out as any variation or any unknown/missing value:

    case $TERM in
        ""|unknown|dumb|dial*|tty|cons25|*ansi*)
            TERM=ansi
            ;;
        linux)
            stty intr '^c'
            stty erase '^?'
            tput smpch
            ;;
        rxvt)
            stty intr '^c'
            stty erase '^?'
            ;;
    esac


the cons25 being replaced by ansi is for when I telnet or ssh in from a
freebsd box. freebsd's console TERM value is "cons25" and it's practically
identical to scoansi so there is no need to add "cons25" to sco's terminfo &
sco's, bbx's, fp's termcaps to support this terminal.

for you all that matters is that if the console is setting TERM="scoansi"
that will get detected above and replaced with "ansi" and more programs will
work out of the box with "ansi" than "scoansi". It's easier to change this
than fix every program.

(supporting the statement made earlier that actually sco's ansi came first
and the variations that came later are the ones who deviated from an
existing standard not the other way around)

You could also just put this one line instead of above if you never ssh in
from linux boxes:

case $TERM in ""|unknown|dumb|dial*|tty|*ansi*) TERM=ansi ;; esac ; export
TERM

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani