optparse
optparse copied to clipboard
nk412
Simple command line arguments parser for BASH
The previous API requires a temporary file to be created and sourced, which might be a problem in restricted environments where accessing to temporary directories are restricted or where file...
I'm packaging this project for the Nix package manager's [Nixpkgs](https://github.com/NixOS/nixpkgs) repo. Packages that doesn't have a version pinned using git tag or releases are treated differently there. Besides, it would...
`--with-default-names` no longer works, this is gone in brew, please provide a solution
It seems only courteous to alert the maintainers of this project to https://unix.stackexchange.com/q/253481/135943 which specifically asks about one of the pieces of code in it.
``` optparse.define short=A long=extraDockerRunArgs desc="optional, quoted string of extra docker run argument flags/values" variable=EXTRA_DOCKER_RUN_ARGS default="" ``` `mycmd.sh -A "--memory=\"256M\" --cpu-shares=\"100\""` results in `Unrecognized long option: --memory="256M" --cpu-shares="100"`
can this support more than 26 options? I.E. the limit of possibilities for the `-short` option, does that take anything other than alphas?
Cloning the repo and running `$ bash sample_head.sh --help` produces the following output, including a syntax error: ``` $ bash sample_head.sh --help optparse.bash: line 140: #NL: syntax error: operand expected...
on occasion i need to reparse the options so we would need to without the defaults. ``` command -c config_file -i override ``` where it would read the config file...
I'm making some fixes / enhancements to optparse & created a basic test suite using BATS to ensure everything is working. Would be nice to get this all into master...
Fix for the '--' issue identified in nk412/optparse#9 and reference in pull request nk412/optparse#10 However, this fix is **just** for the '--' issue. Pull request nk412/optparse#10 adds other unnecessary changes.