Jawher Moussa

@wmark: Just to be sure I'm understanding correctly: you're suggesting that parsing should stop as soon as something erroneous is encountered, right ? If that's the case, this approach is...

On a side note, I've been thinking (from a while ago) of a way to handle arbitrary flags (not necessarily declared before-hand). Something like with the `head` or `tail` commands...

@skyzyx Here's how mow.cli parses the spec string `[--cluster= [--only-env=] | --all]`:  However,by adding parenthesis to get this spec string: `[(--cluster= [--only-env=]) | --all]`,...

Hi @oakad. Wouldn't the usual panic recovery technic be enough ? ```go defer func() { if r := recover(); r != nil { fmt.Printf("recovered: %s\n", r) } }() app.Run(os.Args) ```

I understand. I'll need to think a bit on how to go about implementing this: If I want want to keep the original panic stack, I'll have to find another...

How about implementing a custom multi-valued option type to represent an ordered slice of typed file filters (include or exclude) ? Something like: ```go type Type string const ( Include...

Ah, I see. Since each option stores its value in a separate variable, the order is indeed lost. I'll have to think on how best to accommodate such a use...

@wkhere Thank you for your suggestions ! Could you clarify a bit the following points ? * argparse's metavar: just a string, e.g. `bool` or `true|false` which when help is...

Hi 👋 Sorry for the delay. I'm playing with different options to expose the CLI's structure (commands, options, arguments) without trying it to the internal data structures. I'll hopefull have...

@skyzyx Thank you for your patience 🤗 I just pushed a branch with a PoC of an app model: https://github.com/jawher/mow.cli/pull/106 I would be grateful if you could play with it...