Hi, I haven't tested your code (will do this week-end) and I think it's a
good idea.
I already do what your module proposes to help with but I haven't had the
idea to make a module out of it.
my format looks like this:
my @flags_and_help =
(
'h|help' => \$pbs_config->{DISPLAY_HELP}
'Displays this help.',
''",
'hs|help_switch=s' => \$pbs_config->{DISPLAY_SWITCH_HELP},
'Displays help for the given switch.',
''" ,
'c|colorize' => \$PBS::Output::colorize,
'Colorize output.',
<<EOT ,
If Term::AnsiColor is installed on your system, use this switch to
colorize PBS output.
PBS has default colors but colorization is not turned on by default.
Colors can be defined through switches (try pbs -h | grep color) or
....
Check 'Term::AnsiColor' for more information.
EOT
So I have a short help which I use like this:
$> pbs -h | grep what_I_am_looking_for
which is very useful to remember some switch (I have well over 150 of those)
and a long help used like this:
$>pbs -hs colorize
lately I have added, to the application, a self search feature that extract
and display information embeded in pod.
I believe it would be good to let the users of you module define what , how
many types and how they want the help. So even my format is limiting.
You could still have some default values and types for the user that is
happy with what comes standard with the module.
Searching within the switch help is very usefull and should be supported.
I'll contribute a patch if you wish.
Cheers, Nadim.
Please CC me at [EMAIL PROTECTED] as I don't have news at home.
