I think what you're suggesting is overkill.

The user should RTFM as needed.

That said, what you need to do is parse the pod.

From my own embarrassing hack ( LEOCHARRE::CLI2 is decent) : 

# BEIGN HELP , USAGE, MAN ETC

sub main::man {

   if( defined $main::usage ){
      my $output = $main::usage;
      print STDERR "$output\n";
   }

   elsif( defined &main::usage ){
      my $output = main::usage();
      print STDERR "$output\n";
   }

   else {
       my $name = main::_scriptname();
      print `man $name`; 
   }

   exit;
}
# END HELP

sub main::_scriptname{
    my $name = $0 or return;
    $name=~s/^.+\///;
    return $name;
}

[download]

Of course, you need to take this further, you need to actually parse the pod.. Look into PPI- Maybe PPI can help isolate the pod, and you can pick at it with something like Pod::Simple::SimpleTree

In reply to Re: Parsing Pod::Text by leocharre
in thread Parsing Pod::Text by neo1491

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.