Term::ANSIColor in a Win2K cmd window?

wolfger has asked for the wisdom of the Perl Monks concerning the following question:

Greetings again, fellow monks. The more I use Perl, the more questions I have... But this can only be a good thing! Today on the Perl Advent Calender the featured module is Term::ANSIColor. Of course, this sounded like a great idea to me, and I immediately wanted to try it out. Unfortunately, the output yielded color codes, rather than actual colors. :-( This is really more of a Windows question than a Perl question, but it never hurts to ask. How can I get this module to work for me on my work laptop? Do I need a 3rd-party term window with ANSI support, or is there some way to get the cmd prompt to handle color codes?

--
Linux, sci-fi, and Nat Torkington, all at Penguicon 3.0

Comment on Term::ANSIColor in a Win2K cmd window?

Replies are listed 'Best First'.
Re: Term::ANSIColor in a Win2K cmd window? by gellyfish (Monsignor) on Dec 02, 2004 at 13:25 UTC
In the old days one had to load the ANSI.SYS driver in order to have the ANSI terminal emulation work in DOS/Windows Command Prompt. You might find this article useful - it will still apply to Windows 2000 and XP as far as I can tell. /J\	[reply]
Re: Term::ANSIColor in a Win2K cmd window? by Anonymous Monk on Dec 02, 2004 at 14:20 UTC
Blinking Win32::Console::ANSI	[reply]
Re^2: Term::ANSIColor in a Win2K cmd window? by wolfger (Deacon) on Dec 02, 2004 at 15:19 UTC
Well, it may have been a Windows problem, but it had a Perl solution. :-) Thanks for the pointer to Win32::Console::ANSI. That did the trick. -- Linux, sci-fi, and Nat Torkington, all at Penguicon 3.0	[reply]