why the getopt doesn't work well in my mac os?

Question

In bash: I input the command：

getopt -l name,data -- --namd

and the output is

-- name,pp -- --namd

input :

getopt -l name,data -- --name

the output alse

-- name,pp -- --name

why it dosen't tell me the err when i input getopt -l name,data -- --namd?

You may also want to look at the `getopts` builtin command, which is generally easier to work with. At least, I think so. — larsks, Aug 02 '12 at 12:53
@larsks, but I want to deal the long parameter. such as: cmd --path /user --name qiushuitian -d -p 100 — qiushuitian, Aug 02 '12 at 14:11

score 9 · Accepted Answer · answered Aug 02 '12 at 13:02

9

The problem is that on the mac, getopt is the BSD based getopt, rather than the gnu-based getopt.

It doesn't understand long options. It's not that it 'doesn't work well', it's that it's not designed to do what you asked.

answered Aug 02 '12 at 13:02

Anya Shenanigans

Thanks. But if I want to deal with the long options, how can I do? Must I analyze the parameter myself? – qiushuitian Aug 03 '12 at 03:27
2

You can install gnu getopt from macports - http://stackoverflow.com/questions/402377/using-getopts-in-bash-shell-script-to-get-long-and-short-command-line-options – Anya Shenanigans Aug 03 '12 at 07:33

1 Answers1