The which in Perl discussion made me think about all the stuff in my PATH. So I decided to find if I have any conflicts in my PATH...

In case you were wondering, it turned out I had /usr/bin in my PATH twice :-(

#!/usr/bin/perl -w
use strict;
my %locations;
foreach my $path (split(/:/,$ENV{PATH})) {
  opendir(DIR,$path) 
    || die "Directory $path in your PATH can not be opened:$!\n";
  foreach my $file (readdir(DIR)) {
    next if -d "$path/$file"; # not sure if this is really needed...
    next unless -x _;
    push (@{$locations{$file}},$path);
  }
}

foreach my $file (sort keys %locations) {
  print "$file :",join(" ",@{$locations{$file}}),"\n" 
    if scalar($#{$locations{$file}});
}

[download]

In reply to Conflicts in my PATH by matija

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.