Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From: "Griff Miller II" <griff.miller@oplink.net>
Newsgroups: gnu.bash.bug
Subject: Re: Possible bug in getopts when required argument is not supplied
Date: Fri, 13 Nov 2015 13:57:10 -0600
Lines: 22
Approved: bug-bash@gnu.org
Message-ID: <mailman.2285.1447444647.7904.bug-bash@gnu.org>
References: <535058272b68c9459882c6bd4565b428.squirrel@webmail.oplink.net> <20151113185616.GH27325@eeg.ccf.org>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Cc: bug-bash@gnu.org, Griff Miller II <griff.miller@oplink.net>
To: "Greg Wooledge" <wooledg@eeg.ccf.org>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <20151113185616.GH27325@eeg.ccf.org>
User-Agent: SquirrelMail/1.5.2 [SVN]
Precedence: list
Xref: csiph.com gnu.bash.bug:11878

On Fri, November 13, 2015 12:56 pm, Greg Wooledge wrote:
> On Fri, Nov 13, 2015 at 10:13:15AM -0600, Griff Miller II wrote:
>
>> % ./myscript -a -b b
>>
>>
>> Note that in the last run, getopts does not detect that nothing was
>> passed via -a, even though -a requires it. Instead, it thinks the next
>> switch (-b) is the value of -a. Perhaps this was a conscious decision,
>>
>
> Yes, it is.
>
>
> If you want your script to disallow arguments of -a that begin with a
> hyphen character, you will have to check for that yourself.

Well, there you go.  :)  Thanks for replying. I do currently have just
such a workaround implemented. Any chance of making this behavior clearer
in the man page?