Perhaps this is beyond the scope of what pod2usage is intended to do
I've found Pod::Usage great for simple stuff, and sometimes finicky for more complicated stuff, so that would be my hand-waving reply :-) Some POD parsers were originally written in the olden days so they are not great fun to debug and figure out.
I usually just have a short SYNOPSIS with a verbatim block of a brief summary of the command-line args, I try to keep it under half a page, and at the end a note for the user to run perldoc scriptname if they want the long version. That then gives the usual behavior for scriptname --help (a short usage summary), and the entire POD ends up being structured the same way a lot of man pages are (a short usage summary in the Synopsis followed by the details).
In reply to Re: pod2usage() -sections omits marked-up text from =head lines?
by Anonymous Monk
in thread pod2usage() -sections omits marked-up text from =head lines?
by karlberry
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |