[root@localhost ~]# rm --help
Usage: rm [OPTION]... FILE...
Remove (unlink) the FILE(s).
-f, --force ignore nonexistent files, never prompt
-r, -R, --recursive remove directories and their contents recursively
-v, --verbose explain what is being done
...
By default, rm d
[root@localhost ~]# rm --help
Usage: rm [OPTION]... FILE...
Remove (unlink) the FILE(s).
-f, --force ignore nonexistent files, never prompt
-r, -R, --recursive remove directories and their contents recursively
-v, --verbose explain what is being done
...
By default, rm d
[root@localhost ~]# rm --help
Usage: rm [OPTION]... FILE...
Remove (unlink) the FILE(s).
-f, --force ignore nonexistent files, never prompt
-r, -R, --recursive remove directories and their contents recursively
-v, --verbose explain what is being done
...
By default, rm d
I assume you're aware it's valid to have two initializers for the same
variable.? I often use -v and -verbose to both modify flagVerbose.
var flagVerbose bool
func init() {
boolVar(&flagVerbose,"v"
boolVar(&flagVerbose "verbose"
}
Other than that I don't see what your package is act
thanks for posting. About adding to the stdlib: I don't think non backwards
compatible changes can ever be added to the go stdlib.
On Thursday, August 18, 2016 at 10:11:35 PM UTC+12, Ally Dale wrote:
>
> Hi, everyone,
> I have create a package named cmdline to extend std.flag based on Go
> s
