usage: Put positional args direclty in usage string

[kamalmarhubi]

If I have just one optional positional arg say FILE, it should show up directly in the usage string, instead of as [ARGS]. If it's required it shows up as <FILE>, but if it's optional I get [ARGS] with it listed under the ARGS section in help. I'd prefer [FILE] directly in usage.

[kbknapp]

I hadn't thought about that before, I like that. My only concern would be handling conflicts, or if users get confused why adding more positional args makes them disappear from the default usage string.

Thoughts?

[kamalmarhubi]

My only concern would be handling conflicts

As in different args with the same value_name?

if users get confused why adding more positional args makes them disappear from the default usage string.

Perhaps it could be an app or arg setting then?

[kbknapp]

As in different args with the same value_name?

No, I mean if the positional arg conflicts with specific options or flags. But on the flip side, the user would a message with new usage string so I guess it's not that big a deal.

Perhaps it could be an app or arg setting then?

I thought about that, but I think its benign enough to be the default and add a setting to disable this feature.

[kbknapp]

#520 fixes this