comment on

Are you using the git-bash console ?

There you'll have which and a Perl installation and Unix paths notation.

That doesn't effect the normal cmd.exe unless you change PATH to point to the git utilities. ( I never tried this)

Anyway perldoc -l MODUL will point you to your Perl's installation directory.

For instance the doc location of a core module like warnings always works.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

s/-t/-l/

Fired up my Win box and inside cmd.exe it works

D:\>perldoc -l warnings
C:\Perl_524\lib\warnings.pm
[download]

But seems that git-bash comes without perldoc

$ perldoc -l warnings
Can't locate Pod/Perldoc.pm in @INC ...
[download]

But the following works on both variations, provided you swap ' and " accordingly for cmd.exe

$ perl -Mwarnings -e 'print $INC{"warnings.pm"}'
/usr/share/perl5/core_perl/warnings.pm
[download]

D:\>perl -Mwarnings -e "print $INC{q'warnings.pm'}"
C:/Perl_524/lib/warnings.pm
[download]

ANYWAY DON'T TRY TO UNINSTALL git's Perl.

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks