Drop-in replacement for Go's flag package, implementing POSIX/GNU-style --flags.

This is very useful in conjunction with FlagSets for supporting "commands" with differing sets of options.

eg.

cmd --loglevel=debug ls -la
cmd run --command=/bin/ls

Where the arguments to the ls and run commands are in different FlagSets. Without this capability, FlagSets are quite a bit less useful.

I personally prefer this as the default, but it may not be what you want. If that is the case I can modify the patch to optionally allow interspersed options via an alternate Parse() entry point.

Most cli tools I use have a space character to delimit the flag and it's option, and it would be cool to be able to do so for pflag. I realize this would be yet another departure from the flag stdlib, but it would definitely be cool to have.

I tried just changing https://github.com/ogier/pflag/blob/master/flag.go#L429 to a space character, but it seems I'll also need to change something in FlagSet, just not sure where. Would be happy to make a PR adding another method that configures this and make the requisite changes given some direction :)

consider a command foo --bar --baz

where --bar is defined, but --baz isn't.

pflag prints unknown flag: --bar even though the actual offending flag is --baz

This is part of the Ubuntu distribution for ppc64le. This helps us simplify testing later when distributions are re-building and re-releasing, For more info please tag @gerrith3.

I'm having some trouble passing an element of a map to stringtostring, where the value may or may not contain equal signs, quotes, and/or commas. It seems there is no normative passing, quoting, escaping mechanism.

The documentation says the items won't be split on commas, but if they contain an equal sign, they are. Then to have the commas and quotes preserved, they must be quoted: but this won't be correct if they don't contain an equal sign, no?

Is there any functionality to parse ranges as flags. For example the namp tool takes a range of ports to scan nmap HOST -p 10-100

This would scan ports in the range 10 to 100. Similar functionalities being implemented would be helpful!

Hi, is there a way to don't lose the -h flag that in the standard library produce a list of all flags registered?

Hi have register a flag:

var userID *int = pflag.IntP("user", "u", 0, "User ID")

flag.Parse()

fmt.Printf("User ID %v\n", *userID)

if I run go run main.go -h I get this message:

Usage of /tmp/go-build252835213/command-line-arguments/_obj/exe/main:
exit status 2

Thanks

Now we cover complete integer and float types, including (u)int(8,16,32,64) and float(32,64).

Two data types from net package are also included: net.IP and net.IPMask.

Hello,

I'm wondering if it's possible to change source of flags. For the moment you seems to use os.Args to parse flags. Is it possible to change this source like giving an array ?

Thanks :)

I wanted flags that can only be specified as -f and not --f. Mainly because it allows for the help to look better. I think this type of flag is mostly useful for bool flags, but I added convenience methods/functions for all flag types by adding S to the name: BoolS. For BoolS("f", false, "blah") the help is: -f=false: blah.

This is very useful in conjunction with FlagSets for supporting "commands" with differing sets of options.

eg.

cmd --loglevel=debug ls -la
cmd run --command=/bin/ls

Where the arguments to the ls and run commands are in different FlagSets. Without this capability, FlagSets are quite a bit less useful.

If I've got multiple flags, say, like this:

--user="something"
--language="blah"
--starCount=2
....
...
...

then how to check which flag has been given input in the cli? Because different flag has different functionality.

Removes Init method to standardize on NewFlagSet.

This method can be used to check if a flag was specified by the user.

(I noticed a similar attempt was done in #8 but didn't know at the time I wrote this, which is arguably a smaller changeset)

Hello,

I would like to confirm if this package is still maintained or basically the maintained fork is https://github.com/spf13/pflag.

In case that the mentioned fork is the maintained version, could you please add a note at the beginning of the README; I think that it will be very useful for the people who lands in the repo browsing in Google.

Many thanks.

Hi, things is I want parse 2 bool args, but there is a positional arg, like this:

gofind ./ -d -f

./ is a positional arg, but once I add this , -d -f cannot parse which is default by false , so it should be true if set. But always false. How to parse them? and what if I want using

-d -f as -df just like tar -xvf? Many thanks if can get a reply or advise!

I spent a bit scratching my head trying to figure out why my flags weren't being set/parsed correctly. The issue was that I was using f := pflag.FlagSet{} instead of f := pflag.NewFlagSet(...)

Making an interface would be a simple way to make the behavior more obvious. Thanks!