Tired of scrambling around @INC when you want to see a module's code? Let Perl find it!

Save this in a file in your search path (I called it vipm -- guess what editor I use). Then you can just say

vipm Apache::Registry CGI #or vipm Apache/Registry.pm CGI.pm
or whatever.

Arguments starting with - are passed through. There's not a lot of error checking; give it stupid arguments, it'll probably do stupid things.

Share and enjoy.

#! /usr/bin/perl -w # # Find a module and edit it. Arguments should be either # "Perl" style: Apache::Registry # or "path" style: Apache/Registry.pm # # Any arguments starting with - are passed to editor unchanged. # foreach (@ARGV) { next if /^-/; s|/|::|g if s/\.pm$//; eval "require $_" or die "Module $_ didn't load\n"; s|::|/|g; } exec $ENV{EDITOR} || '/bin/vi', map {/^-/? $_ : $INC{$_ . '.pm'} } @AR +GV;

In reply to Find and edit module by VSarkiss

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.