Re: Wrong explanation of getopts

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Wrong explanation of getopts
Date	2019-09-16 11:23 -0400
Message-ID	<mailman.359.1568647414.2190.bug-bash@gnu.org> (permalink)
References	<0bc4f0f2-863d-5c42-76d8-857f74a1d8fa@gmx.de> <e6d4d8ef-ba67-ba24-f6cf-db0b83d611ae@case.edu>

Show all headers | View raw

On 9/15/19 3:57 PM, Roland Illig wrote:
> The help text of getopts says:
> 
>>   Getopts normally parses the positional parameters ($0 - $9), but if
>>   more arguments are given, they are parsed instead.
> 
> The positional parameter $0 (is it even called that way) is not parsed
> by getopts. Its only use might be in error messages, but I'm not sure
> about it.

You're right; getopts doesn't use $0 at this time.

-- 
``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/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Wrong explanation of getopts Chet Ramey <chet.ramey@case.edu> - 2019-09-16 11:23 -0400

csiph-web