/[public]/getopt/trunk/getopt.1
ViewVC logotype

Diff of /getopt/trunk/getopt.1

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 263 Revision 365
1.TH GETOPT 1 "May 31, 1997" Linux "" 1.TH GETOPT "1" "June 2012" "Linux" "User Commands"
2.SH NAME 2.SH NAME
3getopt \- parse command options (enhanced) 3getopt \- parse command options (enhanced)
4.SH SYNOPSIS 4.SH SYNOPSIS
5.BI getopt
5.BR getopt " optstring parameters" 6.I optstring parameters
6 7.br
7.BR getopt " [options] [" \-\- "] optstring parameters" 8.B getopt
8 9.RI [ options ]
9.BR getopt " [options] " \-o | \-\-options " optstring [options] [" \-\- "] parameters" 10.RB [ \-\- ]
11.I optstring parameters
12.br
13.B getopt
14.RI [ options ]
15.BR \-o | \-\-options
16.I optstring
17.RI [ options ]
18.RB [ \-\- ]
19.I parameters
10.SH DESCRIPTION 20.SH DESCRIPTION
11.B getopt 21.B getopt
12is used to break up 22is used to break up
13.RI ( parse ) 23.RI ( parse )
14options in command lines for easy parsing by 24options in command lines for easy parsing by shell procedures, and to
15shell procedures, and to check for legal options. 25check for legal options. It uses the
16It uses the
17.SM GNU 26.SM GNU
18.BR getopt (3) 27.BR getopt (3)
19routines to do this. 28routines to do this.
20 29.PP
21The parameters 30The parameters
22.B getopt 31.B getopt
23is called with can be divided into two parts: options 32is called with can be divided into two parts: options which modify
24which modify the way getopt will parse 33the way
34.B getopt
35will do the parsing
25.RI ( options 36.RI "(the " options
26and 37and the
27.I \-o|\-\-options optstring 38.I optstring
28in the 39in the
29.BR SYNOPSIS), 40.BR SYNOPSIS ),
30and the parameters which are to be 41and the parameters which are to be parsed
31parsed
32.RI ( parameters 42.RI ( parameters
33in the 43in the
34.BR SYNOPSIS). 44.BR SYNOPSIS ).
35The second part will start at the first non\-option parameter 45The second part will start at the first non\-option parameter that is
36that is not an option argument, or after the first occurrence of 46not an option argument, or after the first occurrence of
37.RB ` \-\- '. 47.RB ' \-\- '.
38If no 48If no
39.RB ` \-o ' 49.RB ' \-o '
40or 50or
41.RB ` \-\-options ' 51.RB ' \-\-options '
42option is found in the first part, the first 52option is found in the first part, the first parameter of the second
43parameter of the second part is used as the short options string. 53part is used as the short options string.
44 54.PP
45If the environment variable 55If the environment variable
46.B GETOPT_COMPATIBLE 56.B GETOPT_COMPATIBLE
47is set, or if its first parameter 57is set, or if the first \fIparameter\fR is not an option (does not start
48is not an option (does not start with a 58with a
49.RB ` \- ', 59.RB ' \- ',
50this is the first format in the 60the first format in the
51.BR SYNOPSIS), 61.BR SYNOPSIS ),
52.B getopt 62.B getopt
53will generate output that is compatible with that of other versions of 63will generate output that is compatible with that of other versions of
54.BR getopt (1). 64.BR getopt (1).
55It will still do parameter shuffling and recognize optional 65It will still do parameter shuffling and recognize optional arguments
56arguments (see section 66(see section
57.B COMPATIBILITY 67.B COMPATIBILITY
58for more information). 68for more information).
59 69.PP
60Traditional implementations of 70Traditional implementations of
61.BR getopt (1) 71.BR getopt (1)
62are unable to cope with whitespace and other (shell\-specific) special characters 72are unable to cope with whitespace and other (shell\-specific)
63in arguments and non\-option parameters. To solve this problem, this 73special characters in arguments and non\-option parameters. To solve
64implementation can generate 74this problem, this implementation can generate quoted output which
65quoted output which must once again be interpreted by the shell (usually 75must once again be interpreted by the shell (usually by using the
66by using the
67.B eval 76.B eval
68command). This has the effect of preserving those characters, but 77command). This has the effect of preserving those characters, but
69you must call 78you must call
70.B getopt 79.B getopt
71in a way that is no longer compatible with other versions (the second 80in a way that is no longer compatible with other versions (the second
72or third format in the 81or third format in the
73.BR SYNOPSIS). 82.BR SYNOPSIS ).
74To determine whether this enhanced version of 83To determine whether this enhanced version of
75.BR getopt (1) 84.BR getopt (1)
76is installed, a special test option 85is installed, a special test option
77.RB ( \-T ) 86.RB ( \-T )
78can be used. 87can be used.
79.SH OPTIONS 88.SH OPTIONS
89.TP
80.IP "\-a, \-\-alternative" 90.BR \-a , " \-\-alternative"
81Allow long options to start with a single 91Allow long options to start with a single
82.RB ` \- '. 92.RB ' \- '.
93.TP
83.IP "\-h, \-\-help" 94.BR \-h , " \-\-help"
84Output a small usage guide and exit succesfully. No other output is generated. 95Display help text and exit. No other output is generated.
96.TP
85.IP "\-l, \-\-longoptions longopts" 97.BR \-l , " \-\-longoptions \fIlongopts\fP"
86The long (multi\-character) options to be recognized. 98The long (multi\-character) options to be recognized. More than one
87More than one option name
88may be specified at once, by separating the names with commas. This option 99option name may be specified at once, by separating the names with
89may be given more than once, the 100commas. This option may be given more than once, the
90.I longopts 101.I longopts
91are cumulative. 102are cumulative. Each long option name in
92Each long option name
93in
94.I longopts 103.I longopts
95may be followed by one colon to indicate it has a required argument,and by two colons to indicate it has an optional argument.
96.IP "\-n, \-\-name progname"
97The name that will be used by the
98.BR getopt (3)
99routines when it reports errors. Note that errors of
100.BR getopt (1)
101are still reported as coming from getopt.
102.IP "\-o, \-\-options shortopts"
103The short (one\-character) options to be recognized. If this option is not
104found, the first parameter of
105.B getopt
106that does not start with
107a
108.RB ` \- '
109(and is not an option argument) is used as the short options string.
110Each short option character
111in
112.I shortopts
113may be followed by one colon to indicate it has a required argument, 104may be followed by one colon to indicate it has a required argument,
114and by two colons to indicate it has an optional argument. 105and by two colons to indicate it has an optional argument.
106.TP
107.BR \-n , " \-\-name \fIprogname\fP"
108The name that will be used by the
109.BR getopt (3)
110routines when it reports errors. Note that errors of
111.BR getopt (1)
112are still reported as coming from getopt.
113.TP
114.BR \-o , " \-\-options \fIshortopts\fP"
115The short (one\-character) options to be recognized. If this option
116is not found, the first parameter of
117.B getopt
118that does not start with a
119.RB ' \- '
120(and is not an option argument) is used as the short options string.
121Each short option character in
122.I shortopts
123may be followed by one colon to indicate it has a required argument,
124and by two colons to indicate it has an optional argument. The first
115The first character of shortopts may be 125character of shortopts may be
116.RB ` + ' 126.RB ' + '
117or 127or
118.RB ` \- ' 128.RB ' \- '
119to influence the way
120options are parsed and output is generated (see section 129to influence the way options are parsed and output is generated (see
130section
121.B SCANNING MODES 131.B SCANNING MODES
122for details). 132for details).
133.TP
123.IP "\-q, \-\-quiet" 134.BR \-q , " \-\-quiet"
124Disable error reporting by getopt(3). 135Disable error reporting by getopt(3).
136.TP
125.IP "\-Q, \-\-quiet\-output" 137.BR \-Q , " \-\-quiet\-output"
126Do not generate normal output. Errors are still reported by 138Do not generate normal output. Errors are still reported by
127.BR getopt (3), 139.BR getopt (3),
128unless you also use 140unless you also use
129.IR \-q . 141.BR \-q .
130.IP "\-s, \-\-shell shell" 142.TP
131Set quoting conventions to those of shell. If no \-s argument is found, 143.BR \-s , " \-\-shell \fIshell\fP"
132the 144Set quoting conventions to those of \fIshell\fR.
145If the \fB\-s\fR option is not given, the
133.SM BASH 146.SM BASH
134conventions are used. Valid arguments are currently 147conventions are used. Valid arguments are currently
135.RB ` sh ' 148.RB ' sh '
136.RB ` bash ', 149.RB ' bash ',
137.RB ` csh ', 150.RB ' csh ',
138and 151and
139.RB ` tcsh '. 152.RB ' tcsh '.
153.TP
140.IP "\-u, \-\-unquoted" 154.BR \-u , " \-\-unquoted"
141Do not quote the output. Note that whitespace and special (shell\-dependent) 155Do not quote the output. Note that whitespace and special
142characters can cause havoc in this mode (like they do with other 156(shell\-dependent) characters can cause havoc in this mode (like they
157do with other
143.BR getopt (1) 158.BR getopt (1)
144implementations). 159implementations).
145.IP "\-T \-\-test" 160.TP
161.BR \-T , " \-\-test"
146Test if your 162Test if your
147.BR getopt (1) 163.BR getopt (1)
148is this enhanced version or an old version. This generates no output, 164is this enhanced version or an old version. This generates no
149and sets the error status to 4. Other implementations of 165output, and sets the error status to 4. Other implementations of
150.BR getopt (1), 166.BR getopt (1),
151and this version if the environment variable 167and this version if the environment variable
152.B GETOPT_COMPATIBLE 168.B GETOPT_COMPATIBLE
153is set, 169is set, will return
154will return
155.RB ` \-\- ' 170.RB ' \-\- '
156and error status 0. 171and error status 0.
172.TP
157.IP "\-V, \-\-version" 173.BR \-V , " \-\-version"
158Output version information and exit succesfully. No other output is generated. 174Display version information and exit. No other output is generated.
159.SH PARSING 175.SH PARSING
160This section specifies the format of the second part of the parameters of 176This section specifies the format of the second part of the
177parameters of
161.B getopt 178.B getopt
162(the 179(the
163.I parameters 180.I parameters
164in the 181in the
165.BR SYNOPSIS ). 182.BR SYNOPSIS ).
166The next section 183The next section
167.RB ( OUTPUT ) 184.RB ( OUTPUT )
168describes the output that is 185describes the output that is generated. These parameters were
169generated. These parameters were typically the parameters a shell function 186typically the parameters a shell function was called with. Care must
170was called with.
171Care must be taken that each parameter the shell function was 187be taken that each parameter the shell function was called with
172called with corresponds to exactly one parameter in the parameter list of 188corresponds to exactly one parameter in the parameter list of
173.B getopt 189.B getopt
174(see the 190(see the
175.BR EXAMPLES ). 191.BR EXAMPLES ).
176All parsing is done by the GNU 192All parsing is done by the GNU
177.BR getopt (3) 193.BR getopt (3)
178routines. 194routines.
179 195.PP
180The parameters are parsed from left to right. Each parameter is classified as a 196The parameters are parsed from left to right. Each parameter is
181short option, a long option, an argument to an option, 197classified as a short option, a long option, an argument to an
182or a non\-option parameter. 198option, or a non\-option parameter.
183 199.PP
184A simple short option is a 200A simple short option is a
185.RB ` \- ' 201.RB ' \- '
186followed by a short option character. If 202followed by a short option character. If the option has a required
187the option has a required argument, it may be written directly after the option 203argument, it may be written directly after the option character or as
188character or as the next parameter (ie. separated by whitespace on the 204the next parameter (i.e. separated by whitespace on the command
189command line). If the
190option has an optional argument, it must be written directly after the 205line). If the option has an optional argument, it must be written
191option character if present. 206directly after the option character if present.
192 207.PP
193It is possible to specify several short options after one 208It is possible to specify several short options after one
194.RB ` \- ', 209.RB ' \- ',
195as long as all (except possibly the last) do not have required or optional 210as long as all (except possibly the last) do not have required or
196arguments. 211optional arguments.
197 212.PP
198A long option normally begins with 213A long option normally begins with
199.RB ` \-\- ' 214.RB ' \-\- '
200followed by the long option name. 215followed by the long option name. If the option has a required
201If the option has a required argument, it may be written directly after 216argument, it may be written directly after the long option name,
202the long option name, separated by 217separated by
203.RB ` = ', 218.RB ' = ',
204or as the next argument (ie. separated by whitespace on the command line). 219or as the next argument (i.e. separated by whitespace on the command
205If the option has an optional argument, it must 220line). If the option has an optional argument, it must be written
206be written directly after the long option name, separated by 221directly after the long option name, separated by
207.RB ` = ', 222.RB ' = ',
208if present (if you add the 223if present (if you add the
209.RB ` = ' 224.RB ' = '
210but nothing behind it, it is interpreted 225but nothing behind it, it is interpreted as if no argument was
211as if no argument was present; this is a slight bug, see the 226present; this is a slight bug, see the
212.BR BUGS ). 227.BR BUGS ).
213Long options may be abbreviated, as long as the abbreviation is not 228Long options may be abbreviated, as long as the abbreviation is not
214ambiguous. 229ambiguous.
215 230.PP
216Each parameter not starting with a 231Each parameter not starting with a
217.RB ` \- ', 232.RB ' \- ',
218and not a required argument of 233and not a required argument of a previous option, is a non\-option
219a previous option, is a non\-option parameter. Each parameter after 234parameter. Each parameter after a
220a
221.RB ` \-\- ' 235.RB ' \-\- '
222parameter is always interpreted as a non\-option parameter. 236parameter is always interpreted as a non\-option parameter. If the
223If the environment variable 237environment variable
224.B POSIXLY_CORRECT 238.B POSIXLY_CORRECT
225is set, or if the short 239is set, or if the short option string started with a
226option string started with a
227.RB ` + ', 240.RB ' + ',
228all remaining parameters are interpreted 241all remaining parameters are interpreted as non\-option parameters as
229as non\-option parameters as soon as the first non\-option parameter is 242soon as the first non\-option parameter is found.
230found.
231.SH OUTPUT 243.SH OUTPUT
232Output is generated for each element described in the previous section. 244Output is generated for each element described in the previous
233Output is done 245section. Output is done in the same order as the elements are
234in the same order as the elements are specified in the input, except 246specified in the input, except for non\-option parameters. Output
235for non\-option parameters. Output can be done in 247can be done in
236.I compatible 248.I compatible
237.RI ( unquoted ) 249.RI ( unquoted )
238mode, or in such way that whitespace and other special characters within 250mode, or in such way that whitespace and other special characters
239arguments and non\-option parameters are preserved (see 251within arguments and non\-option parameters are preserved (see
240.BR QUOTING ). 252.BR QUOTING ).
241When the output is processed in the shell script, it will seem to be 253When the output is processed in the shell script, it will seem to be
242composed of distinct elements that can be processed one by one (by using the 254composed of distinct elements that can be processed one by one (by
243shift command in most shell languages). This is imperfect in unquoted mode, 255using the shift command in most shell languages). This is imperfect
244as elements can be split at unexpected places if they contain whitespace 256in unquoted mode, as elements can be split at unexpected places if
245or special characters. 257they contain whitespace or special characters.
246 258.PP
247If there are problems parsing the parameters, for example because a 259If there are problems parsing the parameters, for example because a
248required argument is not found or an option is not recognized, an error 260required argument is not found or an option is not recognized, an
249will be reported on stderr, there will be no output for the offending 261error will be reported on stderr, there will be no output for the
250element, and a non\-zero error status is returned. 262offending element, and a non\-zero error status is returned.
251 263.PP
252For a short option, a single 264For a short option, a single
253.RB ` \- ' 265.RB ' \- '
254and the option character are generated 266and the option character are generated as one parameter. If the
255as one parameter. If the option has an argument, the next 267option has an argument, the next parameter will be the argument. If
256parameter will be the argument. If the option takes an optional argument, 268the option takes an optional argument, but none was found, the next
257but none was found, the next parameter will be generated but be empty in 269parameter will be generated but be empty in quoting mode, but no
258quoting mode,
259but no second parameter will be generated in unquoted (compatible) mode. 270second parameter will be generated in unquoted (compatible) mode.
260Note that many other 271Note that many other
261.BR getopt (1) 272.BR getopt (1)
262implemetations do not support optional arguments. 273implementations do not support optional arguments.
263 274.PP
264If several short options were specified after a single 275If several short options were specified after a single
265.RB ` \- ', 276.RB ' \- ',
266each will be present in the output as a separate parameter. 277each will be present in the output as a separate parameter.
267 278.PP
268For a long option, 279For a long option,
269.RB ` \-\- ' 280.RB ' \-\- '
270and the full option name are generated as one 281and the full option name are generated as one parameter. This is
271parameter. This is done regardless whether the option was abbreviated or 282done regardless whether the option was abbreviated or specified with
272specified with a single 283a single
273.RB ` \- ' 284.RB ' \- '
274in the input. Arguments are handled as with short options. 285in the input. Arguments are handled as with short options.
275 286.PP
276Normally, no non\-option parameters output is generated until all options 287Normally, no non\-option parameters output is generated until all
277and their arguments have been generated. Then 288options and their arguments have been generated. Then
278.RB ` \-\- ' 289.RB ' \-\- '
279is generated as a 290is generated as a single parameter, and after it the non\-option
280single parameter, and after it the non\-option parameters in the order 291parameters in the order they were found, each as a separate
281they were found, each as a separate parameter.
282Only if the first character of the short options string was a 292parameter. Only if the first character of the short options string
293was a
283.RB ` \- ', 294.RB ' \- ',
284non\-option parameter output is generated at the place they are found in the 295non\-option parameter output is generated at the place they are found
285input (this is not supported if the first format of the 296in the input (this is not supported if the first format of the
286.B SYNOPSIS 297.B SYNOPSIS
287is used; in that case all preceding occurrences of 298is used; in that case all preceding occurrences of
288.RB ` \- ' 299.RB ' \- '
289and 300and
290.RB ` + ' 301.RB ' + '
291are ignored). 302are ignored).
292.SH QUOTING 303.SH QUOTING
293In compatible mode, whitespace or 'special' characters in arguments or 304In compatible mode, whitespace or 'special' characters in arguments
294non\-option parameters are not handled correctly. As the output is 305or non\-option parameters are not handled correctly. As the output
295fed to the shell script, the script does not know how it is supposed to break 306is fed to the shell script, the script does not know how it is
296the output into separate parameters. To circumvent this 307supposed to break the output into separate parameters. To circumvent
297problem, this implementation offers quoting. The idea is that output 308this problem, this implementation offers quoting. The idea is that
298is generated with quotes around each parameter. When this output is once 309output is generated with quotes around each parameter. When this
299again fed to the shell (usually by a shell 310output is once again fed to the shell (usually by a shell
300.B eval 311.B eval
301command), it is split correctly into separate parameters. 312command), it is split correctly into separate parameters.
302 313.PP
303Quoting is not enabled if the environment variable 314Quoting is not enabled if the environment variable
304.B GETOPT_COMPATIBLE 315.B GETOPT_COMPATIBLE
305is set, if the first form of the 316is set, if the first form of the
306.B SYNOPSIS 317.B SYNOPSIS
307is used, or if the option 318is used, or if the option
308.RB ` \-u ' 319.RB ' \-u '
309is found. 320is found.
310 321.PP
311Different shells use different quoting conventions. You can use the 322Different shells use different quoting conventions. You can use the
312.RB ` \-s ' 323.RB ' \-s '
313option to select the shell you are using. The following shells are 324option to select the shell you are using. The following shells are
314currently supported: 325currently supported:
315.RB ` sh ', 326.RB ' sh ',
316.RB ` bash ', 327.RB ' bash ',
317.RB ` csh ' 328.RB ' csh '
318and 329and
319.RB ` tcsh '. 330.RB ' tcsh '.
320Actually, only two `flavors' are distinguished: sh\-like quoting conventions 331Actually, only two 'flavors' are distinguished: sh\-like quoting
321and csh\-like quoting conventions. Chances are that if you use another shell 332conventions and csh\-like quoting conventions. Chances are that if
322script language, one of these flavors can still be used. 333you use another shell script language, one of these flavors can still
323 334be used.
324.SH "SCANNING MODES" 335.SH "SCANNING MODES"
325The first character of the short options string may be a 336The first character of the short options string may be a
326.RB ` \- ' 337.RB ' \- '
327or a 338or a
328.RB ` + ' 339.RB ' + '
329to indicate a special scanning mode. If the first calling form 340to indicate a special scanning mode. If the first calling form in
330in the 341the
331.B SYNOPSIS 342.B SYNOPSIS
332is used they are ignored; the environment variable 343is used they are ignored; the environment variable
333.B POSIXLY_CORRECT 344.B POSIXLY_CORRECT
334is still examined, though. 345is still examined, though.
335 346.PP
336If the first character is 347If the first character is
337.RB ` + ', 348.RB ' + ',
338or if the environment variable 349or if the environment variable
339.B POSIXLY_CORRECT 350.B POSIXLY_CORRECT
340is set, parsing stops as soon as the first non\-option parameter 351is set, parsing stops as soon as the first non\-option parameter
341(ie. a parameter that does not start with a 352(i.e. a parameter that does not start with a
342.RB ` \- ') 353.RB ' \- ')
343is found that 354is found that is not an option argument. The remaining parameters
344is not an option argument. The remaining parameters are all interpreted as 355are all interpreted as non\-option parameters.
345non\-option parameters. 356.PP
346
347If the first character is a 357If the first character is a
348.RB ` \- ', 358.RB ' \- ',
349non\-option parameters are outputed at the place where they are found; in normal 359non\-option parameters are outputted at the place where they are
350operation, they are all collected at the end of output after a 360found; in normal operation, they are all collected at the end of
361output after a
351.RB ` \-\- ' 362.RB ' \-\- '
352parameter has been generated. Note that this 363parameter has been generated. Note that this
353.RB ` \-\- ' 364.RB ' \-\- '
354parameter is still generated, but it will always be the last parameter in 365parameter is still generated, but it will always be the last
355this mode. 366parameter in this mode.
356.SH COMPATIBILITY 367.SH COMPATIBILITY
357This version of 368This version of
358.BR getopt (1) 369.BR getopt (1)
359is written to be as compatible as possible to 370is written to be as compatible as possible to other versions.
360other versions. Usually you can just replace them with this version 371Usually you can just replace them with this version without any
361without any modifications, and with some advantages. 372modifications, and with some advantages.
362 373.PP
363If the first character of the first parameter of getopt is not a 374If the first character of the first parameter of getopt is not a
364.RB ` \- ', 375.RB ' \- ',
376.B getopt
365getopt goes into compatibility mode. It will interpret its first parameter as 377goes into compatibility mode. It will interpret its first
366the string of short options, and all other arguments will be parsed. It 378parameter as the string of short options, and all other arguments
367will still do parameter shuffling (ie. all non\-option parameters are outputed 379will be parsed. It will still do parameter shuffling (i.e. all
368at the end), unless the environment variable 380non\-option parameters are output at the end), unless the
381environment variable
369.B POSIXLY_CORRECT 382.B POSIXLY_CORRECT
370is set. 383is set.
371 384.PP
372The environment variable 385The environment variable
373.B GETOPT_COMPATIBLE 386.B GETOPT_COMPATIBLE
374forces 387forces
375.B getopt 388.B getopt
376into compatibility mode. Setting both this environment variable and 389into compatibility mode. Setting both this environment variable and
377.B POSIXLY_CORRECT 390.B POSIXLY_CORRECT
378offers 100% compatibility for `difficult' programs. Usually, though, 391offers 100% compatibility for 'difficult' programs. Usually, though,
379neither is needed. 392neither is needed.
380 393.PP
381In compatibility mode, leading 394In compatibility mode, leading
382.RB ` \- ' 395.RB ' \- '
383and 396and
384.RB ` + ' 397.RB ' + '
385characters in the short options string are ignored. 398characters in the short options string are ignored.
386.SH RETURN CODES 399.SH RETURN CODES
387.B getopt 400.B getopt
388returns error code 401returns error code
389.B 0 402.B 0
390for succesful parsing, 403for successful parsing,
391.B 1 404.B 1
392if 405if
393.BR getopt (3) 406.BR getopt (3)
394returns errors, 407returns errors,
395.B 2 408.B 2
396if it does not understand its own parameters, 409if it does not understand its own parameters,
397.B 3 410.B 3
398if an internal error occurs like out\-of\-memory, and 411if an internal error occurs like out\-of\-memory, and
399.B 4 412.B 4
400if it is called with 413if it is called with
401.BR \-T . 414.BR \-T .
402.SH EXAMPLES 415.SH EXAMPLES
403Example scripts for (ba)sh and (t)csh are provided with the 416Example scripts for (ba)sh and (t)csh are provided with the
404.BR getopt (1) 417.BR getopt (1)
405distribution, and are optionally installed in 418distribution, and are optionally installed in
406.B /usr/local/lib/getopt 419.BR /usr/local/share/getopt/
407or 420or
408.BR /usr/lib/getopt . 421.BR /usr/share/getopt/ .
409.SH ENVIRONMENT 422.SH ENVIRONMENT
410.IP POSIXLY_CORRECT 423.IP POSIXLY_CORRECT
411This environment variable is examined by the 424This environment variable is examined by the
412.BR getopt (3) 425.BR getopt (3)
413routines.
414If it is set, parsing stops as soon as a parameter 426routines. If it is set, parsing stops as soon as a parameter is
415is found that is not an option or an option argument. All remaining 427found that is not an option or an option argument. All remaining
416parameters are also interpreted as non\-option parameters, regardless 428parameters are also interpreted as non\-option parameters, regardless
417whether they start with a 429whether they start with a
418.RB ` \- '. 430.RB ' \- '.
419.IP GETOPT_COMPATIBLE 431.IP GETOPT_COMPATIBLE
420Forces 432Forces
421.B getopt 433.B getopt
422to use the first calling format as specified in the 434to use the first calling format as specified in the
423.BR SYNOPSIS . 435.BR SYNOPSIS .
424.SH BUGS 436.SH BUGS
425.BR getopt (3) 437.BR getopt (3)
426can parse long options with optional arguments that are given an empty optional 438can parse long options with optional arguments that are given an
427argument (but can not do this for short options). This 439empty optional argument (but can not do this for short options).
440This
428.BR getopt (1) 441.BR getopt (1)
429treats optional arguments that are empty as if they were not present. 442treats optional arguments that are empty as if they were not present.
430 443.PP
431The syntax if you do not want any short option variables at all is 444The syntax if you do not want any short option variables at all is
432not very intuitive (you have to set them explicitely to the empty 445not very intuitive (you have to set them explicitly to the empty
433string). 446string).
434
435.SH AUTHOR 447.SH AUTHOR
436Frodo Looijaard <frodo@frodo.looijaard.name> 448.MT frodo@frodo.looijaard.name
449Frodo Looijaard
450.ME
437.SH "SEE ALSO" 451.SH "SEE ALSO"
438.BR getopt (3), 452.BR getopt (3),
439.BR bash (1), 453.BR bash (1),
440.BR tcsh (1). 454.BR tcsh (1).
441 455.SH AVAILABILITY
456You can download the latest getopt from
457.UR http://frodo.looijaard.name/project/getopt
458the author's home page
459.UE .
460It is also part of the util-linux package which is available from
461.UR ftp://\:ftp.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
462Linux Kernel Archive
463.UE .

Legend:
Removed from v.263  
changed lines
  Added in v.365

frodo@frodo.looijaard.name
ViewVC Help
Powered by ViewVC 1.1.26