flee@gondor.psu.edu (Felix Lee) (11/06/87)
In article <5187@ncoast.UUCP> allbery@ncoast.UUCP (Brandon Allbery) writes: >As quoted from <6625@brl-smoke.ARPA> by gwyn@brl-smoke.ARPA (Doug Gwyn ): >+--------------- >| The developer is wrong. I know that some people have tried to give >| special semantics to sg#0 and ug#0, but it has never to my knowledge >| been adopted in the official termcap (or terminfo) documentation, >+--------------- System Vr3 curses recognizes the difference between xmc#0 and no xmc at all. The System Vr3 programmer's reference manual documents xmc# (and all the other glitches) much better than all previous manuals. Saying xmc#0 is *not* the same as saying msgr. Msgr just says that the terminal won't take you out of any display modes when you move the cursor or send a newline. The "magic cookie" glitch refers to terminals that use field mark characters on the screen to change display modes, instead of having attribute bits for each character. IBM 3270 terminals are probably the most widespread magic-cookie terminals. "Magic cookie" terminals require a different display algorithm. Say you move to a highlighted area of the screen and print "hello". On a "normal" terminal, "hello" will not be highlighted (if you're not in highlighted mode). On a magic cookie terminal, "hello" will be highlighted, since it's within the area delimited by the "start-highlight" and "end-highlight" magic cookies. Anyone want to know the semantics of xenl/xn? -- Felix Lee flee@gondor.psu.edu {cbosgd,cmcl2}!psuvax1!gondor!flee