03-26-2014, 12:21 PM
I don't think my comment deserves a new thread or even a trac ticket as I may have misunderstood something, but I thought I should at least mention it.
When using cleanup-rules.exe on Win7 64bit I have noticed a difference in the input command, compared to other tools in the set of utilities.
With cleanup-rules.exe I have to use <path to file> instead of "path to file".
Example...
cleanup-rules.exe 2 <path to input file> "path to output file"
Usual way would be...
cleanup-rules.exe 2 "path to input file" "path to output file"
Using "" (quotes) to surround the paths to files is normal for windows and the other utilities as it allows users to have " " (spaces) in their path names. Using < > for the first path to file seems odd especially when they are not required for the path to output file.
This is not a problem once the user knows to use < > but it may confuse new users and it makes cleanup-rules.exe slightly different to the other tools, which may seem odd to people.
Thank you.
When using cleanup-rules.exe on Win7 64bit I have noticed a difference in the input command, compared to other tools in the set of utilities.
With cleanup-rules.exe I have to use <path to file> instead of "path to file".
Example...
cleanup-rules.exe 2 <path to input file> "path to output file"
Usual way would be...
cleanup-rules.exe 2 "path to input file" "path to output file"
Using "" (quotes) to surround the paths to files is normal for windows and the other utilities as it allows users to have " " (spaces) in their path names. Using < > for the first path to file seems odd especially when they are not required for the path to output file.
This is not a problem once the user knows to use < > but it may confuse new users and it makes cleanup-rules.exe slightly different to the other tools, which may seem odd to people.
Thank you.