bitbucket.org/ulfurinn/cli
DOC DRAFT Package cli provides a toolset for writing command line interfaces. This package started off as a fork of package github.com/codegangsta/cli with an aim to enhance shell completion but has diverged since then. Application definition structure is similar but not identical. The following sections briefly describe the main components; see the API index for information on further customization. A minimally viable application looks like this: Options can be used as follows: Any command line argument that cannot be identified and parsed as a named option will be available in Args(), but a formal declaration provides type-specific parsing and better help messages. Named options and positional arguments are declared and accessed through the same interface. Subcommands are created as follows: Like the root command Main, subcommands can have their own options and subcommands. The root command has an implicit "help" subcommand, showing usage instructions. For help on subcommands, it is invoked as "app help subcmd1 subcmd2 ...". Alternatively, every command has an implicit "--help" option that has the same effect. The implicit "help-commands" subcommand prints a recursive list of all declared subcommands. All subcommand and options are available for shell completion. Additionally, they can declare custom completion functions, returning a list of accepted values. The bash completion function is available at https://bitbucket.org/ulfurinn/cli/raw/default/bash_completion; replace $PROG with the name of your executable.
Readme
This package is a fork/rewrite of github.com/codegangsta/cli with the purpose of providing smarter shell completion.
If you want to migrate from github.com/codegangsta/cli, you'll need to make minor changes in your command setup as there are differences in exposed types.
FAQs
DOC DRAFT Package cli provides a toolset for writing command line interfaces. This package started off as a fork of package github.com/codegangsta/cli with an aim to enhance shell completion but has diverged since then. Application definition structure is similar but not identical. The following sections briefly describe the main components; see the API index for information on further customization. A minimally viable application looks like this: Options can be used as follows: Any command line argument that cannot be identified and parsed as a named option will be available in Args(), but a formal declaration provides type-specific parsing and better help messages. Named options and positional arguments are declared and accessed through the same interface. Subcommands are created as follows: Like the root command Main, subcommands can have their own options and subcommands. The root command has an implicit "help" subcommand, showing usage instructions. For help on subcommands, it is invoked as "app help subcmd1 subcmd2 ...". Alternatively, every command has an implicit "--help" option that has the same effect. The implicit "help-commands" subcommand prints a recursive list of all declared subcommands. All subcommand and options are available for shell completion. Additionally, they can declare custom completion functions, returning a list of accepted values. The bash completion function is available at https://bitbucket.org/ulfurinn/cli/raw/default/bash_completion; replace $PROG with the name of your executable.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A hospital in Mobile, Alabama, agreed to a settlement in a landmark ransomware death lawsuit, but is now reportedly reconsidering the agreement and refusing to pay.
Security News
A new report explores how advancements in LLMs are enhancing cyber threats, including polymorphic malware, personalized spearphishing, and the risk of hijacking customer service bots.
Security News
ESLint has approved an RFC that adds support for TypeScript configuration files, which is aimed at improving the developer experience and recognizing changes in the evolving JavaScript ecosystem.
