Re: cpan on mac os x yosemite

Replies are listed 'Best First'.
Re^2: cpan on mac os x yosemite by Anonymous Monk on Apr 05, 2015 at 01:52 UTC
Crossposted at http://stackoverflow.com/questions/29452187/perl-cpan-strange-behavior. I cross-linked this cross-postings for maximum collaboration efficiency	[reply]
Re^2: cpan on mac os x yosemite by abualiga (Scribe) on Apr 05, 2015 at 03:26 UTC
Thanks Anonymous -- that worked. No idea how though. The TERM variable changes from `xterm-256color` to `dumb` and my `alias ls='ls -GpF -h'` does not give color output anymore, but cpan is now visible. And thanks for the post crosslinking tip.	[reply] [d/l] [select]
Re^3: cpan on mac os x yosemite by Anonymous Monk on Apr 05, 2015 at 09:36 UTC
Well :) you could always set term=dumb for perl only through perl options PERL5OPT / sitecustomize... even CPAN/MyConfig.pm ... after all its just an %ENV entry Also, depending on which Term::ReadLine:: you got there might be hints in the bug queue , rt://Term-ReadLine-Perl... or you might submit a bug report	[reply]
Re^4: cpan on mac os x yosemite by abualiga (Scribe) on Apr 05, 2015 at 13:24 UTC
I have installed Term::Readline::Perl; btw did not find any existing bug reports similar to what I have. Adding `term => q[dumb]` to MyConfig.pm does not help. Setting `term_ornaments => q[0]` returns visibility to a cpan shell, but only `export TERM=dumb` fixes the issue for both cpan and perl debugger.	[reply] [d/l] [select]
Re^5: cpan on mac os x yosemite by abualiga (Scribe) on Apr 05, 2015 at 16:23 UTC
Re^3: cpan on mac os x yosemite by abualiga (Scribe) on Apr 05, 2015 at 03:32 UTC
Also, `export TERM=dumb` does not play nice with vim.	[reply] [d/l]