[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Handling getopt for option without optional argument value
From: |
Alex fxmbsw7 Ratchev |
Subject: |
Re: Handling getopt for option without optional argument value |
Date: |
Fri, 23 Jul 2021 17:11:27 +0200 |
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
>
>
- Handling getopt for option without optional argument value, lisa-asket, 2021/07/23
- Re: Handling getopt for option without optional argument value, Greg Wooledge, 2021/07/23
- Re: Handling getopt for option without optional argument value,
Alex fxmbsw7 Ratchev <=
- Re: Handling getopt for option without optional argument value, Greg Wooledge, 2021/07/23
- Handling getopt for option without optional argument value, lisa-asket, 2021/07/23
- Re: Handling getopt for option without optional argument value, Dennis Williamson, 2021/07/23
- Handling getopt for option without optional argument value, lisa-asket, 2021/07/23
- Re: Handling getopt for option without optional argument value, Greg Wooledge, 2021/07/23
- Handling getopt for option without optional argument value, lisa-asket, 2021/07/23
- Re: Handling getopt for option without optional argument value, Chet Ramey, 2021/07/23