FreeFileSync Forum

I agree that using colons is not a good idea, especially in directory names, since that would cause problems if that directory is needed in a path variable. I don't use colons in filenames but the reason I tripped over the bug was that the filename was being created automatically by the save of an e...

As far as I can see that error shouldn't show up. I can quite easily create a file with a colon in the name (using Linux Mint with Cinnamon desktop or the terminal) and the file system has no problem with it and no errors appear, so the OS shouldn't be giving an error to FFS. I suppose it could be c...

The issue is that a colon is a valid character in a filename in Linux. I can create valid file names containing a colon without any trouble. Thunderbird already strips the colon under Windows since it is invalid in Windows, but doesn't strip it in Linux because it is valid.

I started receiving error messages on certain files on Linux. The error was: Cannot write file "xx path to file xx~random characters. ffs_tmp" EINVAL: Invalid argument [open] Inspecting the various errors I noted that they all contained a colon character in the filename. This resulted from...