SCO's curses

Warren Tucker wht at n4hgf.Mt-Park.GA.US
Mon Mar 25 16:14:07 AEST 1991


In article <1991Mar22.211749.13292 at robobar.co.uk> ronald at robobar.co.uk (Ronald S H Khoo) writes:
>SCO's 3.2.0 Dev Sys terminfo curses seems to go crazy (*) when fed
>8 bit characters -- 
>(*) "crazy" in this sense: with this program -
>
>	$ cat foo.c
>	#include <curses.h>
>	main()
>	{	initscr();
>		addch(0243);
>		refresh();
>		endwin();
>	}
>I expect a pound sign on an ISO Latin 1 terminal, or a u-acute
>on a PC console.  Instead I get a flashing blinking screen full of
>carets.  Sigh.  Strangely enough, it *does* work when I add a -xenix
>flag, but then GDB doesn't.  Sigh.


The bits above the 0x80 bits are attribute bits in 3.2 curses
and include blink, underline and color.  Look at /usr/include/tinfo.h
at the A_..... definitions and the man page for curses.

There is an A_ALTCHARSET bit you can set, but you may utlimately
be disappointed in using the high 128 video characters.
I only tried for three days before giving up (wanted to use
the ruling characters).  I tried the 'acs' stuff and everything
else in TFM, terminfo.src and header files, but with no luck.
I am still interested in doing this one day.  Until then,
I use the termcap curses, which does not support color or a
host of other nice things, but you can write any video ROM
character from 0x20 to 0xFF.


 
----------------------------------------------------------------------------
Warren Tucker, TuckerWare, Mountain Park, GA         wht at n4hgf.Mt-Park.GA.US
"The computer can't tell you the emotional story.  It can give you the exact
mathematical design, but what's missing is the eyebrows." -- Frank Zappa



More information about the Comp.unix.sysv386 mailing list