[<<]Message[>>]    [<<]Author[>>]    [<<]Subject        [<<]Thread[>>]

Number   :  197
Date     :  2001-06-14
Author   :  Ed Light
Subject  :  Re: XXCOPY New Beta Version (v.2.56.2) ready
Size(KB) :  1


> 
> This version handles some /X parameters which were not anticipated
> 
> /Xdirname\*\ will be treated as equivalent to /Xdirname\*\*
> /Xdirname\?\ will be treated as equivalent to /Xdirname\?\*
> 
> The first line shown above was reported as a bug by Ed Light 
earlier.
> Although we do not consider it a bug (we do concede that the

Kan, in your doc #1 of 2000-01-04 you say:

Exclusion specifier (xspec) syntax (consists of up to 3 parts):
for file, [ dir_spec\ ] [ *\ ] [ ftemplate ]
for dir, [ dir_spec\ ] [ *\ ] [ dtemplate ]
dir_spec is always followed by a backslash (\). It specifies
a directory (or directories with wildcard) which
are relative to the source directory unless it
starts with a \. A wildcard specifier is allowed
only in the last element of dir_spec.
*\ This second part specifies that the exclusion
applies to all subdirectories under dir_spec.


So I read that to read tack *\ onto dir_spec\

like: C:\MYDIR\*\

Does C:\MYDIR\*\* include subdirectories as well as the target 
directory? Or, now that *\ = \*\*, does *\ include the target and 
all subdirectories?

Does the pre-beta version hate *\ and respond to *\* by excluding the 
target and its subdirectories? The doc #1 seemed to me to say that 
*\* does "full directory." That sounded like just the parent 
directory to me.



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.