Term::ANSIColorx::ColorNicknames - nicknames for the ANSI colors
use Term::ANSIColorx::ColorNicknames; # messes with T::AC
use Term::ANSIColor qw(:constants); # exports new nicknames now
I have a hard time remembering the ANSI colors in terms of bolds and regulars, and also find them irritating to type. If I want the color YELLOW, why should I have to type BOLD() . YELLOW() to get it? YELLOW() is really orange colored, yellow should always be bold. Also, the color BLACK is basically useless, on a black background at least, which is my modus operandi, your mileage may vary.
Except where they are intentionally overwritten, the original Term::ANSIColor names should still be exported correctly.
bloodAlias for the color red.
umberAlias for bold red.
skyAlias for bold blue.
oceanReplaces the color cyan, which should be very bright.
lightblueAlias for ocean.
cyanCyan is the bold of the ocean. It's a bright cyan color.
limeBolded green. It's really a lime color.
orange brownOrange. Most correctly, what ANSI calls "yellow", but is really more of a brown-orange.
yellowYellow. Technically bolded yellow.
purpleAlias for magenta. I can never remember which is right, probably thanks to CSS.
violetBolded purple.
blackBolded black. Black, being totally useless on dark backgrounds. This replacement can be disabled with either $ENV{DISABLE_BLACK} or via $Term::ANSIColorx::ColorNicknames::DISABLE_BLACK -- although the later must be invoked before use compiles the nicknames module.
grey greyUnbolded white.
whiteBolded white.
direScary yellow on red warning color.
Q: This is dumb.
A: That's not a question, but you're right. I still use it.
You can report bugs either via rt.cpan.org or via the issue tracking system on github. I'm likely to notice either fairly quickly.
Paul Miller <jettero@cpan.org>
Copyright 2009 Paul Miller -- released under the GPL
perl(1), Term::ANSIColor
