argbash
getoptions
Our great sponsors
| argbash | getoptions | |
|---|---|---|
| 13 | 7 | |
| 1,359 | 367 | |
| - | - | |
| 0.0 | 0.0 | |
| about 2 months ago | 5 months ago | |
| M4 | Shell | |
| GNU General Public License v3.0 or later | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
argbash
-
Is there a recommended alternative to getopts?
Yeah, now that I look at it a bit closer, it is quirky. Not unmanageable, but I think I prefer something like Argparse which generates the parsing code for you using a simpler language.
- Bashkit V1
- BashLib a helpful source file for any script
- Argbash: Bash argument parsing code generator
- GitHub - matejak/argbash: Bash argument parsing code generator
-
Hacker News top posts: Mar 22, 2022
Argbash: Bash argument parsing code generator\ (0 comments)
getoptions
-
Is there a recommended alternative to getopts?
I like to use https://github.com/ko1nksm/getoptions
- jetopt: a dead simple wrapper around getopt you always dreamed of!
- What is the best way to handle flags?
- Adding options to scripts
-
The easiest way to parse arguments using getoptions for bash and shell scripts
A lot of people have been looking for a best practice to use getopt and getopts for long years. A number of methods to parse arguments were thought up, but no perfect solution was found. However, with the advent of the getoptions, that long journey comes to an end.
-
What is the best practice for handling parameters and flags in a bash script?
Why not use a library instead of implementing it yourself? I wrote getoptions (not getopt or getopts) which many option syntaxes can be easily supported. A lot of options are no longer an obstacle, and there is no need to use another inappropriate language for such a trivial reasons.
- [POSIX] How to Implement --args and How Should Usage Be Formatted
What are some alternatives?
bash-argsparse - An high level argument parsing library for bash
shellspec - A full-featured BDD unit testing framework for bash, ksh, zsh, dash and all POSIX shells
docopts - Shell interpreter for docopt, the command-line interface description language.
shflags - shFlags is a port of the Google gflags library for Unix shell.
modernish - Modernish is a library for writing robust, portable, readable, and powerful programs for POSIX-based shells and utilities.
kingpin - CONTRIBUTIONS ONLY: A Go (golang) command line and flag parser
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
jetopt - A friendly wrapper around getopt
argparse-bash - Use python's argparse module in shell scripts
bash_opts - SImple Bash options parser
bashew - bash script micro-framework - from small stand-alone script to complex projects with CI/CD and testing