Re: Handling getopt for option without optional argument value

[Chet Ramey]

On 7/23/21 11:43 AM, Greg Wooledge wrote:

> The getopts (note the 's') builtin command replaces getopt, and is not
> broken.  Use that instead.  Or, if you need to handle --gnu-long-opts
> or -findopts, write your own option parser.  Or don't write the program
> in bash in the first place.  Or STOP FEELING THAT YOU NEED --gnu-long-opts
> or -findopts in your program.  Just... don't do it.
>
> People make their own lives SO much more complicated than they need to be.
> I don't understand why.

To be fair, you don't know their full requirements. It's all about fitting
the tool to your requirements.

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/