Optparse hanging infinitely & support for multiple usage of the same flag about optparse-applicative HOT 5 CLOSED

It is possible, but you can't repeat an option with a default value, because in that case you get an infinite list as a result, and that makes the parser diverge. Just remove value "" from your parser and it will work. It doesn't make sense to have a default there, anyway.

from optparse-applicative.

Thank you very much! I'm sorry for posting an incorrect bug report.

2013/11/19 Paolo Capriotti [email protected]

It is possible, but you can't repeat an option with a default value,
because in that case you get an infinite list as a result, and that makes
the parser diverge. Just remove value "" from your parser and it will
work. It doesn't make sense to have a default there, anyway.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/58#issuecomment-28778138
.

from optparse-applicative.

i stumbled upon this same problem today. i tried a clumsy option (many str) and got a scary runtime loop. this seems like a noob trap, i propose to improve the README with this example, i'll put a quick patch together

from optparse-applicative.

actually the best solution would probably be a function like manyStrOption = many strOption, where the haddock can explain that this is a simple alias. to me this seems the more findable way to avoid similar error to new users of the library, and make adoption easier ... i see that you kept the interface very dry and orthogonal though so you probably want to keep it so

from optparse-applicative.

it could be modified as in #295 but it's not very visible, maybe we could have some examples of this usage elsewhere, or point to a guide which goes through applicative parsing?

from optparse-applicative.