Thanks! That is indeed the trigger. If I switch to a session with the compiler configured and the behaviour disappears. Another bloody stupid decision. Now I'll have to start a compiler session even if I just want to check the latest varsions of my packages.

Wait, you're annoyed by the color and not by having to press Ctrl-C, setup your compiler and relaunch cpan?

you're annoyed by the color

I'm annoyed that the colorisation doesn't repect my existing setup.

If they changed the foreground color leaving my existing background intact (subject to no white-on-white scenario), I would probably have said "That's cool!" and used it.

I might have even lived with them changing the background color, so long as they set the background color of the entire screen so you don't end up with this red or green on black in a sea of white, which is completely unreadable. (Well, maybe!)

I'm annoyed that when you quit, they do not restore my originals setting. This is trivial to implement.

I'm annoyed that there is no simple way to turn it off.

I'm annoyed that this experimental feature is on by default, rather than opt-in.

having to press Ctrl-C

Hitting ^C isn't enough. Because they don't restore the original settings, once you've left cpan, you have to reset your colors and clear the screen before you can read what you've typed.

Complicated further by the fact that I use different colors for different types of session--32-bit perl; 64-bit perl; 32-bit compiler; 64-bit compiler; debug builds; release builds. once they've messed with things, I then have to remember what the appropriate values are to restore them. Or throw away the session along with any information buffered on the screen amd in the session history buffers and start a new one.

and not by ..., setup your compiler and relaunch cpan?

I'm not quite sure why you think that doesn't annoy me? The sentence preceding the one you've quoted is a fairly strong indication that I'm not too happy about that either.

In the end, the provision of a simple color [on|off] command (with the default off!), would be just so easy to implement and far better than the current 10 steps. (Which don't even work!)

---

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)

(Note that with the 32-bit build 1006 om XP, I get no escape sequences. I don't have your problem at all even though the error comes up in colour.)

The sentence preceding the one you've quoted

I'm confused. There is no such sentence. I quoted your first sentence. I just looked at all the parent posts and you didn't say anything at all about the compiler there either.

Hitting ^C isn't enough

I don't follow here either. Not enough for what?

Not enough to prevent the compiler from installing? Works for me.

Not enough to prevent the colour problem? Isn't it *too* much to prevent the colour problem? If you don't hit Ctrl-C, it installs a compiler and the issue becomes moot for future runs, right?

Complicated further by the fact that I use different colors for different types of session

I wonder how you achieve this. It's very likely an incompatibility with whatever provides your colour support.