in reply to Re^6: They've fscked with CPAN.pm again
in thread They've fscked with CPAN.pm again

(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.

  • Comment on Re^7: They've fscked with CPAN.pm again

Replies are listed 'Best First'.
Re^8: They've fscked with CPAN.pm again
by BrowserUk (Patriarch) on Sep 11, 2009 at 11:53 UTC

    Oh dear. You are very confused aren't you.

    By "start a compiler session", I mean: "start a cmd session and run the appropriate command to set up my compiler.", before issuing the cpan command, thereby preventing it from coming to the wrong decision--that I do not have a compiler--and colorising output and all the other stuff that follows on from that. It never gets to the point of downloading anything, because my firewall prevents it, by asking me if I want to allow it.

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

    cmd.exe! color f9 or whatever else I choose.

    Or more simply, make a cmd shortcut, give it an appropriate name. Right-click the icon and select properties dialog. Set up the window layout; colors; edit-mode; command; short-cut key et. al. to your preferences. Now each time you start a session with that icon or its short-cut sequence, you get those colors etc. Simple. Compatible with everything. Except those things that don't respect/restore my choices--like the lastest version of cpan.

    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.
[reply]
[d/l]
[select]

      I believe CPAN mostly uses whatever Term::Readline implementation it can find. If you set the environment variable $ENV{PERL_RL}="Perl o=0" (as suggested by Term::ReadLine or set $ENV{TERM}="Dumb", that should prevent whatever Readline library you get from trying to make its own changes.

[reply]
[d/l]
[select]
[reply]

      By "start a compiler session", I mean:

      I know. vcvars32 or whatever.

[reply]
[d/l]
        I know.

        Then I am utterly mystified by your original comment and this entire subthread. But don't bother explaining further, because it doesn't matter. syphilis identified the trigger for the behaviour and by avoiding that, I avoid the problem.

        I'd greatly prefer a way to simply disable the colorisation entirely, but that would seem to require too much.

        I'd also greatly prefer that whomever decided that if they can't "detect" my compiler, that it is a good idea to install one, didn't repeat the mistakes of the past by going the same route as they did by downloading the ancient version of nmake.exe and trying to use that, (despite that a newer and more capable version was available on the system via the path), when it was long known that it couldn't handle the generated makefiles. But that persisted long after the problem with was pointed out, so I doubt this will be any different.

[reply]
[d/l]

In Section Seekers of Perl Wisdom