Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • What really striked me is that you globally set TERM=dumb. This is imho a very bad thing, because it was interfering with my cygwin until I finally noticed where it was going from. I think setting global environment is a bad thing, it would be much better to provide a batch file that sets all necessary variables and then leaves command prompt. Users who need it globally will set it themselves and it won't unnecessarily clobber environment for others. Also, when will you publish Perl::Dist::Strawberry on cpan (or whatever else I need to build strawberry myself)?
    • > Users who need it globally will set it themselves and it won't unnecessarily clobber environment for others.

      The entire concept of Strawberry is that there are no additional steps required to get it into a working state.

      The problem is that most people will NOT set TERM=dumb themselves, because most Windows uses aren't familiar with hacking things like the environment themselves.

      It falls back on universal education as a crutch.

      For cygwin users, you are already a step above the normal standard, and as a g
    • Thank you for the problem report. I found it using Google and it helped me confirm what the problem was. I'd been thinking strangenesses like Strawberry tromping on DLLs or something like that, not just sneaky ENVVAR settings.

      Strawberry setting TERM=dumb is bad. Grrr.