I rewrote parts of the script and called it pmdesc3. It overcomes the above mentioned flaws. Output can be sorted and formated. It has a POD included. pmdesc3 is part of the VIM-plugin perl-support.vim (script # 556) and can be found at http://vim.sourceforge.net/scripts/script.php?script_id=556
Oh dear. Let me quote MJD’s File of Good Advice…
#11911 You wrote the same thing twice here. The cardinal rule of programming is that you never ever write the same thing twice.
Copy-pasting bits all over the code is not a good idea.
In any case, I’ve fixed your complaints and posted a new version at lspm — list names and descriptions of Perl modules in a directory. It doesn’t have sorting, because I don’t see the point of implementing that as an option that won’t work on systems where you can pipe output to another process anyway, but it does address all the problems you brought up and adds a bonus feature too. The output should be more readily parsable, as well, although it doesn’t look the same as in your version.
Makeshifts last the longest.
-
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.
|
