Alternate character modes on magic_cookie_glitch terminals (long)

Phong Vo[drew] kpv at ulysses.att.com
Mon Mar 4 12:36:42 AEST 1991


In article <10513 at scolex.sco.COM>, staceyc at sco.COM (Stacey Campbell) writes:
: 
: becomes clear.  Your qvt101 entry contains the numeric capability
: xmc#0.  The guy who wrote System V.3.2 curses claims that it deals
: with magic cookies correctly (he posts occasionally to Usenet),
: though I have yet to see a scrap of documentation that explains
: what is required of the terminfo file and the curses program (obviously
: something, otherwise your program would work).
: 
He's about to do that again :-).
On terminals with magic cookies, you must define "xmg" for terminfo
(or "sg" for termcap) for curses to work correctly.
You do not need to do anything else.

: I am somewhat confused by the 0 in xmc#0, the manual says the numeric
: value to xmc is the "number of blank characters left by smso or
: rmso".  If this value is zero then it would seem that there is no
: magic cookie required, therefore xmc should be removed.  Perhaps
: the 0 is special.  Either way, if xmc#0 is removed from the qvt101+so
: terminfo file the program will emit rmacs.  The curses source implements 
: in a number of places;
: 
xmc defines two attributes: (1) the number of blanks left by smso&rmso,
and (2) the fact that characters output in the region between smso
and rmso will be hilited even if the cursor moves out of that
region, then moves back in for output. Attribute (2) is the reason for xmc#0.
It is common to the HP26* family of terminals.



More information about the Comp.unix.programmer mailing list