-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Pádraig Brady on 12/22/2008 6:55 AM: > Well I wouldn't treat -n differently if one must be able to specify both -f > and -i. > But does POSIX really specify that? I can't see it from a quick read. > All I can see are a mention of the -HLP options:
Huh? http://www.opengroup.org/onlinepubs/9699919799/utilities/mv.html only specified -i and -f, and none of -HLP. Oh, you were looking at cp. But still, the synopsis on http://www.opengroup.org/onlinepubs/9699919799/utilities/cp.html lists three forms: cp [-Pfip] source_file target_file cp [-Pfip] source_file... target cp -R [-H|-L|-P] [-fip] source_file... target By convention, options that are mutually exclusive are called out with separator bars, all other options may be specified simultaneously. http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html#tag_12_01 Therefore, POSIX requires support for 'cp -i -f' and 'cp -f -i', but leaves behavior unspecified for 'cp -H' (the only POSIX use of -H requires - -R; we silently ignore it when -R is omitted, but are allowed to issue an error) and 'cp -R -H -L' (-H and -L are mutually exclusive; we silently accept the last of the conflicting options, but are allowed to issue an error). - -- Don't work too hard, make some time for fun as well! Eric Blake [email protected] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklPoSMACgkQ84KuGfSFAYBcYwCgvNFOn5YQ0KztWHnfVVpzPTt+ V+kAoMaaB7Fpub7tzH6gqlwOsIUSWgpB =Rb4W -----END PGP SIGNATURE----- _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
