Handling getopt for option without optional argument value
From:
lisa-asket
Subject:
Handling getopt for option without optional argument value
Date:
Fri, 23 Jul 2021 17:17:01 +0200 (CEST)
Tho approach should be to fix getopt if there are problems with it, no?
From: Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com>
To: help-bash <help-bash@gnu.org>
Subject: Re: Handling getopt for option without optional argument value
Date: 23/07/2021 17:11:27 Europe/Paris
i agree, craparg
for this i have keywords to eval, in my bashlink sys, easy to stack short
code, .. gotta work on it
On Fri, Jul 23, 2021, 17:04 Greg Wooledge <greg@wooledge.org> wrote:
> On Fri, Jul 23, 2021 at 04:22:04PM +0200, lisa-asket@perso.be wrote:
> > opts=$(getopt -o "$shortopts" -l "$longopts" -n "${0##*/}" -- "$@")
>
> Fail. Never use getopt! It's broken by design.
>
>https://mywiki.wooledge.org/BashFAQ/035
>
>