I created shell completion scripts for dzil
. The completion that is shipped with Dist::Zilla only completes subcommands, and only is for bash, as far as I can see.
My scripts also complete options, and show the description of subcommands and options.
(If dzil commands change, I have to update this, too, of course.)
I created this with https://metacpan.org/pod/App::AppSpec
$ git clone https://github.com/perlpunk/shell-completions.git
$ cd shell-completions
$ source bash/dzil.bash
$ dzil <TAB>
add -- add modules to an existing dist
authordeps -- list your distributions author dependencies
build -- build your dist
clean -- clean up after build, test, or install
commands -- list the applications commands
help -- Show command help
install -- install your dist
listdeps -- print your distributions prerequisites
new -- mint a new dist
nop -- do nothing: initialize dzil, then exit
release -- release your dist
run -- run stuff in a dir where your dist is built
setup -- set up a basic global config file
smoke -- smoke your dist
test -- test your dist
$ dzil test --<TAB>
--all -- enables the RELEASE_TESTING, AUTOMATED_TESTING, EX
+TENDED_TESTING and AUTHOR_TESTING env variables
--author -- enables the AUTHOR_TESTING env variable
--automated -- enables the AUTOMATED_TESTING env variable (defaul
--extended -- enables the EXTENDED_TESTING env variable
--help -- Show command help
--jobs -- number of parallel test jobs to run
--keep-build-dir -- keep the build directory even after a success
--keep -- keep the build directory even after a success
--lib-inc -- additional @INC dirs
--release -- enables the RELEASE_TESTING env variable
--test-verbose -- enables verbose testing (TEST_VERBOSE env variable
+ on Makefile.PL, --verbose on Build.PL
--verbose -- log additional output
--verbose-plugin -- log additional output from some plugins only
# put zsh/_dzil into a directory which is read by
# zsh completions, or add this directory to your .zshrc:
# fpath=("$HOME/path/to/shell-completions/zsh" $fpath)
# log in again
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||