On Wed, Jan 04, 2023 at 01:54:21PM +0100, наб wrote: > > AFAICT, after trawling through the Issue 8 Draft 2.1, > there are no special provisions for unset/OPTIND, Well it says this regarding OPTIND: : If the application sets OPTIND to the value 1, a new set of parameters : can be used: either the current positional parameters or new arg : values. Any other attempt to invoke getopts multiple times in a single : shell execution environment with parameters (positional parameters : or arg operands) that are not the same in all invocations, or with an : OPTIND value modified to be a value other than 1, produces unspecified : results. Unsetting OPTIND ought to do the same thing as setting it to "", which produces unspecified results and I see nothing wrong with printing an error in this case. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt