Either one individually works. The interactive mode that uses Curses works fine so long as I don't try to turn on color, and Term::ANSIColor works fine in the non-interactive query-only mode that doesn't use Curses. However, they won't work together. Curses::has_colors() stubbornly returns false in terminals that I know full well not only support color, but support color in curses-based programs. I've updated my system curses library to ncurses-5.3, and updated to the latest release of Curses.pm, to no avail. Last night I updated to perl-5.8 in the hope that this was one of the many bugs fixed, only to find that Curses.pm won't even build under Perl 5.8.
I seek enlightenment as to why Curses.pm does not believe in color-capable terminals. I've heard it said, but have been unable to confirm, that this is because although it ostensibly supports all the functions, Curses.pm does not actually support color. Is this actually the case? And if so, is it possible for me to use ncurses functions directly through the syscall interface to achieve my desired ends of color text in a curses window?
(My copies of the books of the sainted scribes of O'Reilly are, sadly, in storage until I find work again.)
In reply to Curses.pm with Term::ANSIColor by Llew_Llaw_Gyffes
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |