FFS gives warning comparing 2 files with same name

[hotcore]

Hi,

when I run FFS on Windows, FFS warns that a file abc.txt compared with ABC.txt is equal, but the casing is different.

Since (in Windows) abc.txt and ABC.txt are considered equal, I'd like very much to have an option to ignore case in file or folder names.

Is there a way to achieve this?

Best wishes and TIA,
AvW

[xCSxXenon]

Ignore errors doesn't achieve this?

[hotcore]

Of course it does. But that is not so nice, because then I'll miss severe errors as well ...

[xCSxXenon]

Change the casing I suppose. How many files are like this?
Also, you said is is considered equal in FFS, so wouldn't an option to ignore casing be pointless?

[hotcore]

No, not FFS but Windows-OS regards file/folder names with the same contents and the same name (but different casing) as the same. E.g. 2 text files Ab.txt and aB.txt having same context really are the same.

BTW, I only see this happen with a client that sometimes feels the need to change casing for some file/folder. I now know how to "correct" the "conflict" by manually make the casing equal for both file/folder names.

FFS is obviously a bit biased towards Linux and other OS-es that regard different casing in files/folders as different files/folders, because it issues a warning for a "conflict" which is not a conflict in Windows OS at all!

So, for Windows users an FFS option to ignore case differences in file/folder names, when contents are the same, would be very nice!

[xCSxXenon]

Aha, I see the predicament more clearly! I am all for more options, but I can only see the problem where you have Ab.txt and aB.txt trying to sync to the same file

[Zenju]

You're probably using "Update" variant. In this case you need to set a sync direction for "conflicts", this will get rid of the warning.