- CONFIGURATION FILE
- COPYRIGHT AND LICENSE
dump-getopt-long-subcommand-script - Run a Getopt::Long::Subcommand-based script but only to dump the spec
This document describes version 0.002 of dump-getopt-long-subcommand-script (from Perl distribution App-GetoptLongSubcommandUtils), released on 2016-10-27.
% dump-getopt-long-subcommand-script [options] <filename>
This function runs a CLI script that uses
Getopt::Long::Subcommand but monkey-patches beforehand so that
run() will dump data structure and then exit. The goal is to get the object without actually running the script.
This can be used to gather information about the script and then generate documentation about it or do other things (e.g.
App::shcompgen to generate a completion script for the original script).
CLI script needs to use
Getopt::Long::Subcommand. This is detected currently by a simple regex. If script is not detected as using
Getopt::Long, status 412 is returned.
Will return the
* marks required options.
- --filename=s*, -f
Path to the script.
Libraries to unshift to @INC when running script (JSON-encoded).
- --skip-detect, -D
- -1=s@, -I
Libraries to unshift to @INC when running script.
Can be specified multiple times.
Set path to configuration file.
Can be specified multiple times.
Set configuration profile to use.
Do not use any configuration file.
Choose output format, e.g. json, text.
Set output format to json.
When outputing as JSON, strip result envelope.
By default, when outputing as JSON, the full enveloped result is returned, e.g.:
The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use `--naked-res` so you just get:
This script has shell tab completion capability with support for several shells.
To activate bash completion for this script, put:
complete -C dump-getopt-long-subcommand-script dump-getopt-long-subcommand-script
in your bash startup (e.g.
~/.bashrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is recommended, however, that you install shcompgen which allows you to activate completion scripts for several kinds of scripts on multiple shells. Some CPAN distributions (those that are built with Dist::Zilla::Plugin::GenShellCompletion) will even automatically enable shell completion for their included scripts (using
shcompgen) at installation time, so you can immadiately have tab completion.
To activate tcsh completion for this script, put:
complete dump-getopt-long-subcommand-script 'p/*/`dump-getopt-long-subcommand-script`/'
in your tcsh startup (e.g.
~/.tcshrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is also recommended to install
shcompgen (see above).
For fish and zsh, install
shcompgen as described above.
This script can read configuration files. Configuration files are in the format of IOD, which is basically INI with some extra features.
By default, these names are searched for configuration filenames (can be changed using
--config-path): ~/.config/dump-getopt-long-subcommand-script.conf, ~/dump-getopt-long-subcommand-script.conf, or /etc/dump-getopt-long-subcommand-script.conf.
All found files will be read and merged.
To disable searching for configuration files, pass
You can put multiple profiles in a single file by using section names like
[SOMESECTION profile=SOMENAME]. Those sections will only be read if you specify the matching
You can also put configuration for multiple programs inside a single file, and use filter
program=NAME in section names, e.g.
[program=NAME ...] or
[SOMESECTION program=NAME]. The section will then only be used when the reading program matches.
Finally, you can filter a section by environment variable using the filter
env=CONDITION in section names. For example if you only want a section to be read if a certain environment variable is true:
[env=SOMEVAR ...] or
[SOMESECTION env=SOMEVAR ...]. If you only want a section to be read when the value of an environment variable has value equals something:
[env=HOSTNAME=blink ...] or
[SOMESECTION env=HOSTNAME=blink ...]. If you only want a section to be read when the value of an environment variable does not equal something:
[env=HOSTNAME!=blink ...] or
[SOMESECTION env=HOSTNAME!=blink ...]. If you only want a section to be read when an environment variable contains something:
[env=HOSTNAME*=server ...] or
[SOMESECTION env=HOSTNAME*=server ...]. Note that currently due to simplistic parsing, there must not be any whitespace in the value being compared because it marks the beginning of a new section filter or section name.
List of available configuration parameters:
filename (see --filename) format (see --format) libs (see -1) naked_res (see --naked-res) skip_detect (see --skip-detect)
Specify additional command-line options
Please visit the project's homepage at https://metacpan.org/release/App-GetoptLongSubcommandUtils.
Source repository is at https://github.com/perlancar/perl-App-GetoptLongSubcommandUtils.
Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-GetoptLongSubcommandUtils
When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.
This software is copyright (c) 2016 by firstname.lastname@example.org.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.