R. David Murray added the comment:
This behavior is correct:
rdmurray@session:~>getopt a:b:c -a value1 -b value2 -cbanana
-a value1 -b value2 -c -b anana --
--
nosy: +r.david.murray
resolution: -> not a bug
stage: -> resolved
status: open -> closed
__
New submission from Jak:
The getopt library has, what I assume is, some unexpected behaviour when adding
extra text to command line parameter that getopt expects as a flag.
Using input parameters a, b and c as an example below, where a and b both take
values and c is a flag.
Example code:
opt
