From: MINAMI H. <mi...@mi...> - 2005-01-02 04:44:51
|
On Sat, 2005-01-01 at 20:57 -0500, Ian Ward wrote: > On Sun, 2005-02-01 at 09:58 +0900, MINAMI Hirokazu wrote: > > I couldn't find a demo that uses "start_color" under > > python2.3-2.3.4/Demo/curses and not sure what the problem is. > > Could you prepare some tiny test case? > > Ah, you're right. The demos call curses.wrapper, which calls > start_color for color terminals. > > Here is a test case: ... I've tried your script on the default setting and on "mlterm -f white -b black". When default color (black on white) is used, the cursor couldn't be seen because it's rendered by black on black background. In the latter case (white on black), I could see white rectangle. These result seems to be identical to xterm/rxvt. Are you requesting to draw cursor differently to be always visible? I'm afraid it may rather annoying in some cases. > Without start_color the cursor is visible. > > > BTW, cursor state(invis/norm) currently doesn't save/restored > > and are sheared between normal/alternate screen. > > Are they intentional ?> Sato san > > I'm not sure what you mean by "intentional". Would you rephrase the > question? Don't mind. In this case, as far as cursor visibility is not touched, It shouldn't matter anyway. minami |