Copy /n option order

Why do the two copy commands below with "/n" produce different results? The only difference is where on the command line the "/n" is.


Volume in drive C is OS Serial number is 1ce5:1203
Directory of C:\Junk\Bar\*

11/17/2009 5:07p DIR .
11/17/2009 5:07p DIR ..
11/17/2009 5:07p SYMLINKD Sym [C:\Junk\Foo\]
0 bytes in 0 files and 3 dirs
191,257,014,272 bytes free

C:\Junk\Bar>copy /s /e /n /nj * ..\
C:\Junk\Bar\Sym\Foo.txt => C:\Junk\Sym\Foo.txt
1 file would be copied

C:\Junk\Bar>copy /s /e /nj /n * ..\
0 files would be copied

C:\Junk\Bar>copy /s /e /nj * ..\
0 files copied


Vista Home Premium. Take Command 11.00.33.
It seems that all arguments to /N must be given together. Is this WAD? I interpreted the Help's "A /N with one of the following arguments has an alternate meaning" to mean you should only give one at a time.

C:\Junk>erase /s /x /y /Nn /Nt *
TCC: (Sys) There are no more files.
1 file would be deleted

C:\Junk>erase /s /x /y /Nnt *
TCC: (Sys) There are no more files.
Deleting C:\Junk\Foo\Foo.txt
Removing C:\Junk\Foo\
1 file deleted

rconn wrote:
| WAD - you cannot have multiple /N arguments.

Request that you remove this limitation in the next version, not only from
COPY, but from all other commands this rule currently affects. It is very
convenient to be able to have an alias that already includes e.g. /nenst,
and when using the alias (esp. interactively) to add /nj when appropriate,
instead of requiring two separate aliases.

As for the "report without acting" (/n) option, it is most useful
interactively, and as such, its most convenient location is at the end of
the command line, so that a satisfactory command could be recalled with a
single keystroke, and the /n erased with just two more. From my observation
the REN command handles it correctly even when it is so located. I wish this
behavior would be the documented operation for all commands that accept this