WAD New Bug with Wildcards

[Jay Sage]

The command DIR *.pdf displays many files, but with the latest version the command DIR **.pdf displays none. A number of my scripts have stopped working as a result.

 

[vefatica]

The command DIR *.pdf displays many files, but with the latest version the command DIR **.pdf displays none. A number of my scripts have stopped working as a result.

Did you mean DIR **.pdf in both places? Indeed, it returns files in v33 and not in v34.

 

[rconn]

WAD. From the help:

--------------------

All of the TCC file handling commands that support ranges (for example, DIR, PDIR, TREE, COPY, MOVE, etc.) now support fuzzy filename matching using Levenshtein Distances if the filename begins with two asterisks (**filename). The Levenshtein Distance between two words is the minimum number of single-character edits (insertions, deletions or substitutions) required to change one word into the other.

--------------------

A leading "" never had a meaning in filename matches ( is used for subdirectory searches).

If you don't want to use the Levenshtein Distance wildcards, set LVSDistance=0 in your TCMD.INI.

 

[Jay Sage]

OK. Thanks, Rex. I'll either change the INI setting or modify the scripts to prevent adding an asterisk when one is already present.