perceived strangeness with getopt(1,3)

Maybe I'm missing something huge, but getopt(1,3) aren't working the way I think they should. I have a script that I want to take two options, both of which have required arguments. gabby# getopt k:s: -k getopt: option requires an argument -- k -- gabby# getopt k:s: -s getopt: option requires a

Re: perceived strangeness with getopt(1,3)

In message: <009b01c26500$3f7e91a0$[EMAIL PROTECTED]> "Matthew Emmerton" <[EMAIL PROTECTED]> writes: : gabby# getopt k:s: -k -s : -k -s -- : gabby# : : Wha? Neither of these options specified arguments! I guess you could : consider that -k's argument was '-s', but I was pretty sure

Re: perceived strangeness with getopt(1,3)

In the last episode (Sep 25), Matthew Emmerton said: > Maybe I'm missing something huge, but getopt(1,3) aren't working the > way I think they should. > > gabby# getopt k:s: -k -s > -k -s -- > gabby# > > Wha? Neither of these options specified arguments! I guess you > could consider that -k's