]> git.saurik.com Git - apple/shell_cmds.git/blame - getopt/getopt.1
shell_cmds-207.11.1.tar.gz
[apple/shell_cmds.git] / getopt / getopt.1
CommitLineData
9bafe280
A
1.\" $FreeBSD: src/usr.bin/getopt/getopt.1,v 1.15 2002/04/19 23:43:02 charnier Exp $
2.\"
3.Dd April 3, 1999
44bd5ea7
A
4.Dt GETOPT 1
5.Os
6.Sh NAME
7.Nm getopt
8.Nd parse command options
9.Sh SYNOPSIS
9bafe280
A
10.Nm args=\`getopt Ar optstring $*\`
11; errcode=$?; set \-\- $args
44bd5ea7 12.Sh DESCRIPTION
9bafe280 13The
44bd5ea7 14.Nm
9bafe280 15utility is used to break up options in command lines for easy parsing by
44bd5ea7 16shell procedures, and to check for legal options.
9bafe280 17.Ar Optstring
44bd5ea7 18is a string of recognized option letters (see
9bafe280 19.Xr getopt 3 ) ;
44bd5ea7
A
20if a letter is followed by a colon, the option
21is expected to have an argument which may or may not be
22separated from it by white space.
23The special option
9bafe280 24.Ql \-\-
44bd5ea7 25is used to delimit the end of the options.
9bafe280 26The
44bd5ea7 27.Nm
9bafe280
A
28utility will place
29.Ql \-\-
44bd5ea7
A
30in the arguments at the end of the options,
31or recognize it if used explicitly.
32The shell arguments
33(\fB$1 $2\fR ...) are reset so that each option is
34preceded by a
9bafe280 35.Ql \-
44bd5ea7
A
36and in its own shell argument;
37each option argument is also in its own shell argument.
9bafe280 38.Sh EXAMPLES
44bd5ea7
A
39The following code fragment shows how one might process the arguments
40for a command that can take the options
9bafe280 41.Fl a
44bd5ea7 42and
9bafe280 43.Fl b ,
44bd5ea7 44and the option
9bafe280 45.Fl o ,
44bd5ea7
A
46which requires an argument.
47.Pp
48.Bd -literal -offset indent
49args=\`getopt abo: $*\`
9bafe280
A
50# you should not use \`getopt abo: "$@"\` since that would parse
51# the arguments differently from what the set command below does.
52if [ $? != 0 ]
44bd5ea7
A
53then
54 echo 'Usage: ...'
55 exit 2
56fi
57set \-\- $args
9bafe280
A
58# You cannot use the set command with a backquoted getopt directly,
59# since the exit code from getopt would be shadowed by those of set,
60# which is zero by definition.
44bd5ea7
A
61for i
62do
63 case "$i"
64 in
65 \-a|\-b)
9bafe280
A
66 echo flag $i set; sflags="${i#-}$sflags";
67 shift;;
44bd5ea7 68 \-o)
9bafe280
A
69 echo oarg is "'"$2"'"; oarg="$2"; shift;
70 shift;;
44bd5ea7
A
71 \-\-)
72 shift; break;;
73 esac
74done
9bafe280
A
75echo single-char flags: "'"$sflags"'"
76echo oarg is "'"$oarg"'"
44bd5ea7
A
77.Ed
78.Pp
79This code will accept any of the following as equivalent:
80.Pp
81.Bd -literal -offset indent
82cmd \-aoarg file file
83cmd \-a \-o arg file file
84cmd \-oarg -a file file
85cmd \-a \-oarg \-\- file file
44bd5ea7 86.Pp
9bafe280 87.Ed
44bd5ea7
A
88.Sh SEE ALSO
89.Xr sh 1 ,
90.Xr getopt 3
91.Sh DIAGNOSTICS
9bafe280 92The
44bd5ea7 93.Nm
9bafe280
A
94utility prints an error message on the standard error output and exits with
95status > 0 when it encounters an option letter not included in
96.Ar optstring .
44bd5ea7 97.Sh HISTORY
9bafe280
A
98Written by
99.An Henry Spencer ,
100working from a Bell Labs manual page.
44bd5ea7 101Behavior believed identical to the Bell version.
9bafe280
A
102Example changed in
103.Fx
104version 3.2 and 4.0.
44bd5ea7
A
105.Sh BUGS
106Whatever
107.Xr getopt 3
108has.
109.Pp
110Arguments containing white space or embedded shell metacharacters
9bafe280
A
111generally will not survive intact; this looks easy to fix but
112isn't. People trying to fix
113.Nm
114or the example in this manpage should check the history of this file
115in
116.Fx .
44bd5ea7
A
117.Pp
118The error message for an invalid option is identified as coming
119from
120.Nm
121rather than from the shell procedure containing the invocation
122of
9bafe280 123.Nm ;
44bd5ea7
A
124this again is hard to fix.
125.Pp
126The precise best way to use the
9bafe280 127.Nm set
44bd5ea7
A
128command to set the arguments without disrupting the value(s) of
129shell options varies from one shell version to another.
9bafe280
A
130.Pp
131Each shellscript has to carry complex code to parse arguments halfway
132correcty (like the example presented here). A better getopt-like tool
133would move much of the complexity into the tool and keep the client
134shell scripts simpler.