Allow global flags after command

[fgblomqvist]

This is just a suggestion, but to me it seems logical to allow global flags after the command as well, not only before it.

For example, if you have a verbose flag, -v:
myapp -v server
vs.
myapp server -v

To me the second one does visually make more sense. Are there cases when this is a bad idea (and therefore the reason to why this is not how it is currently implemented)?

[jszwedko]

Hi @fgblomqvist, I agree with you completely. Unfortunately this is baggage that we carry from using the Go stdlib flag library (which stops parsing the moment it hits a non-flag) so we cannot support it unless we were to rip that out and do our own flag parsing (which we have discussed a bit, but is a non-trivial effort). You can see some more conversation about this in #355.

I'll leave this open as a future enhancement though!

[fgblomqvist]

Okay, I see.

[hackergrrl]

The core flag package is BSD licensed, so perhaps the easiest fix would be to include a fork of said package, modified to support intermixed arguments/flags. This has the benefit of keeping the API identical, making the integration simpler than a rewrite or using a different 3rd-party package. Does this sound reasonable?

[jszwedko]

@noffle mmm, that is not a bad idea given the tradeoffs. I'll try to give that a shot in the near future.

Thank you for the suggestion!

[0xdeafcafe]

Also interested in this.

[nikkolasg]

Bump up for this one too !
But in the meantime, @jszwedko : Thank you so far for the good job you've done ;)

[marwan-at-work]

wondering if this issue is still up for a fix :)

[coilysiren]

Given that this is from last year, I think I'm comfortable closing it 🙂 feel free to re-open / open a new issue / comment in support if there's still interest here!