![]() ![]() It would make a lot more sense to replace that one tool with one that understands folders than to build a Rube Goldberg machine to auto-sync folders into a flat list. However, if you want to compare the whole folders contents, you should use third-party tool like Winmerge or Free Commander. This only compares files and folders number. With this and your other thread (which are both really the same question, I think?), it seems like you are layering on more and more tools and complexity in an attempt to work around a fairly ridiculous limitation of the "database" tool you are using. The easiest way is to compare them manually by doing right click on the folders separately > Properties > Compare 'Size, Size on Disk and Contains' on both folders. This takes much more time of course as all files are checked in detail. ![]() Document.Compare to compare it against the one from Folder B. Synching the copies is the same job as synching the originals, and that's the part that's problematic. To compare two folders you can do: rsync -avun SOURCE TARGET And if you are concerned about corrupt files / bit rot there is also the -c option to compare file checksums. To compare two documents, you can either open the source file and then use. All I want is compare two folders and output which files are missing in both folders (compared to the other one). What would adding a TeraCopy copy-and-verify to an intermediate folder get you, other than more complexity? You'd just be duplicating your source folders and then synching the duplicate to your destination, which doesn't seem to get you anywhere. .you can also compare the contents of two folders by adding -rq: diff -rq folder-1 folder-2 Once you enter this commandchanging folder-1 and folder-2 to the folders you want to. I did some research, and there are many diff tools, but I am not interested in comparing the file contents. There's no underlying "basic compare command", it's just the way people want synching to work in almost all cases, and the only way synching can work in the general case (where two files may have the same names in different directories and thus cannot be resolved to a single flat destination). ![]()
0 Comments
Leave a Reply. |