Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15376 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-09-16 11:23 -0400 |
| Last post | 2019-09-16 11:23 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Wrong explanation of getopts Chet Ramey <chet.ramey@case.edu> - 2019-09-16 11:23 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-09-16 11:23 -0400 |
| Subject | Re: Wrong explanation of getopts |
| Message-ID | <mailman.359.1568647414.2190.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web