🚀 go-pugleaf

In article <1894@encore.UUCP> loverso@encore.UUCP (John LoVerso) writes:
>Can someone in-the-know tell me why magic-cookie glitches are not fully
>described in either termcap or terminfo?  Termcap lets you specify
>a magic cookie for standout or underline (sg,ug); terminfo only
>has a capability for one magic cookie value (xmc).  Neither try to
>describe cookies on attributes (blink, bold, dim, invis, rev).

Terminfo intends for "xmc" to cover all mode setting, on the assumption
that if one mode setting uses the "magic cookie" glitch, so will the
others.  Termcap "sg" and "ug" predate the "m*" mode-setting capabilities;
if you have magic cookie glitches for the "m*" capabilities, try setting
both "sg" and "ug" and hope that termcap-using applications are clever
enough to understand that this indicates that the "m*" capabilities are
similarly affected.

It really isn't practicaly for termcap/terminfo to try to anticipate
all the design botches that terminal manufacturers keep coming up
with.  They try to support a variety of implementations of a few simple
models for terminals; anything that does not fit the model cannot be
fully and correctly described by these databases.  Usually, though, a
subset of the terminal's capabilities CAN be described, and this is
what is normally done in such cases.

>My problem is that I've got a Wyse WY75.

Yes, that is your problem.  From what you say, the Wyse WY75 pretends
to support the ANSI mode-setting escape sequence, but doesn't do it
correctly.  If it indeed does not allow individual fields to have
different modes, then the 'm*" capabilities are NOT supported by the
terminal (at least no more than one of them), and your termcap should
reflect this.

You might try using the WYFDAT sequences and set all the "glitch"
capabilities (probably to 1).