jetopt
Friendly options formatter for getopt (by slowpeek)
getoptions
An elegant option/argument parser for shell scripts (full support for bash and all POSIX shells) (by ko1nksm)
| jetopt | getoptions | |
|---|---|---|
| 1 | 7 | |
| 3 | 370 | |
| - | - | |
| 6.0 | 0.0 | |
| about 1 month ago | 5 months ago | |
| Shell | Shell | |
| MIT License | Creative Commons Zero v1.0 Universal |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
jetopt
Posts with mentions or reviews of jetopt.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-24.
-
jetopt: a dead simple wrapper around getopt you always dreamed of!
github repo for jetopt
getoptions
Posts with mentions or reviews of getoptions.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-04.
-
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?
When comparing jetopt and getoptions you can also consider the following projects:
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
argbash - Bash argument parsing code generator
docopts - Shell interpreter for docopt, the command-line interface description language.
shflags - shFlags is a port of the Google gflags library for Unix shell.
kingpin - CONTRIBUTIONS ONLY: A Go (golang) command line and flag parser
bashew - bash script micro-framework - from small stand-alone script to complex projects with CI/CD and testing
sh_libpath - Making shell scripts more robust with libraries
macos-scripts - Various scripts for macOS tasks