Re: [patch] sh.1 getopts inaccurate

2018-11-28 Thread Theo de Raadt
I also agree. > hi > > I'm not familiar with getopts, first time I use it and the man page was > confusing. It says "a colon following an option indicates it may take an > argument". > I understand this as: if I use the string "s:" then I can use "-s" or "-s > something" as it **may** take an

Re: [patch] sh.1 getopts inaccurate

2018-11-28 Thread Philip Guenther
On Wed, Nov 28, 2018 at 10:52 PM Solene Rapenne wrote: > I'm not familiar with getopts, first time I use it and the man page was > confusing. It says "a colon following an option indicates it may take an > argument". > I understand this as: if I use the string "s:" then I can use "-s" or "-s >

[patch] sh.1 getopts inaccurate

2018-11-28 Thread Solene Rapenne
hi I'm not familiar with getopts, first time I use it and the man page was confusing. It says "a colon following an option indicates it may take an argument". I understand this as: if I use the string "s:" then I can use "-s" or "-s something" as it **may** take an argument. But if you use "s:",