On 8 Nov 2003 at 2:12, Frank Heckenbach wrote:
[...]
Obviously there is a problem somewhere. How can a value be ">=2" while being "<=1" at the same time? This is a new mathematical experience for me!
It doesn't say it can be, only that it must be. ;-)
Well, the code in PDCurses-2.6/win32/pdcscrn.c says:
fprintf(stderr,"LINES value must be >= 2 and <= %d: got %d\n", csbi.dwMaximumWindowSize.Y, internal->lines);So, apparently csbi.dwMaximumWindowSize.Y is wrong. It seems to be set a few lines above in
GetConsoleScreenBufferInfo(hConOut, &csbi);
This seems to be a Windows call, so I don't know anything about it, and even if I did, I couldn't debug it. But perhaps it'll help you find out something ...
I have since ascertained that this problem only happens in the MSYS rxvt terminal. Everything works fine at a windows command prompt, and even when bash is loaded directly from the command prompt. Ncurses works well in all situations. So I guess that it might be better to define USE_NCURSES automatically under MSYS.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~african_chief/