PrestoSoft Community

When I compare two folders on the commandline and add the /statsonly option, I get the following output:

2 differences: 20 files, 5 lines
Added items: 0 files and 1 lines in changed files
Deleted items: 0 files and 1 lines in changed files
Changed items: 20 files and 3 lines in changed files

This is the full command: Then I change ONE SINGLE character in one of the files in folder1, everything else remains unchanged, and I get the following output:

3 differences: 25 files, 6 lines
Added items: 0 files and 1 lines in changed files
Deleted items: 0 files and 1 lines in changed files
Changed items: 25 files and 4 lines in changed files

I don't understand this. I would expect exactly one additional change. What do the numbers mean?

Actually, there are exactly 5 (in the first case) or 6 (in the second case) differences, respectively.
Of those differences, 2 are lines which only exist in one of the folders and 3 (first case) resp. 4 (second case) are differences within lines.

Can someone explain?

It's hard to tell without seeing your results. Compare your directories before and after the change in the UI and post your screenshots please.

before the change:



after the 1-letter change:

OK, so do these UI results look right to you? If so, with the same directories and options, do you get 20 and 25 files with the /statsonly option? If so, there must be a bug there. Please confirm.

Thanks for your reply. I have doublechecked and can confirm.

In the UI, the results are perfectly correct as far as I can tell. Likewise, the results in the console are perfectly correct WITHOUT the /statsonly option:
Adding the /statsonly option produces the the described output with 20 or 25 files, respectively, as described above. To get these very different results, I only change one non-whitespace non-comment character in a .cs file, nothing else.
Here is the options file I'm using: http://johannes.unterguggenberger.info/ ... ions_m.txt

Yes, it's a bug that occurs when /f and /statsonly options are used together. The fix will appear in the next build of 9.0 Beta.

That's great! Thank you