I'd never seen it before either until I recently upgraded to 5.10.1. Nothing else changed--in terms of environment settings etc.

Upto and including 5.10.0 (AS1004), I was also blissfully unaware that there was even an option for this. After the upgrade, not only is everything inside the cpan shell unintellible, once you quit out, everything else is too because they fail to put things back how they were. Its just bad programming.

And it rejects any attempts to achieve your settings: 

←[32m
cpan shell -- CPAN exploration and modules installation (v1.9402)
Enter 'h' for help.←[0m

cpan> o conf /color/
←[32m$CPAN::Config options from ←[0m←[32m'C:\Perl64\
+lib/CPAN/Config.pm'←[0m←[32m:←[0m
←[32m←[0m
←[32m    colorize_debug     undef←[0m
←[32m    colorize_output    [undef]←[0m
←[32m    colorize_print     [green]←[0m
←[32m    colorize_warn      [red]←[0m
←[32m←[0m
←[32m←[0m
cpan> o conf colorize_debug undef
←[32m    colorize_debug     [undef]←[0m
←[32mPlease use 'o conf commit' to make the config permanent!&#8
+592;[0m

←[32m←[0m
cpan> o conf colorize_print undef
Term::ANSIColor rejects color[undef]: Invalid attribute name undef at 
+C:\Perl64\lib/CPAN/Shell.pm line 1453


Please choose a different color (Hint: try 'o conf init /color/')
    colorize_print     [undef]←[0m
Term::ANSIColor rejects color[undef]: Invalid attribute name undef at 
+C:\Perl64\lib/CPAN/Shell.pm line 1453


Please choose a different color (Hint: try 'o conf init /color/')
Please use 'o conf commit' to make the config permanent!←[0m

Term::ANSIColor rejects color[undef]: Invalid attribute name undef at 
+C:\Perl64\lib/CPAN/Shell.pm line 1453


Please choose a different color (Hint: try 'o conf init /color/')
←[0m

[download]

Bah humbug! Time to go a hacking again :(

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP PCW It is as I've been saying!(Audio until 20090817)

In reply to Re^4: They've fscked with CPAN.pm again by BrowserUk
in thread They've fscked with CPAN.pm again by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.