My way of doing things isn't "flawed", it's locally adapted to my situation
You are expecting unintended consequences for intentionally doing things in a flawed way because of a situation you fabricated on your own. GotchaI constantly use leading spaces in file and folder names to prioritize them at the top of lists on macOS
LOL I see you're one of "those users"Users don't make mistakes
My way of doing things isn't "flawed", it's locally adapted to my situation ┌(^_^)┘♪└(^_^)┐Using spaces as an organizational method is simply ill-advised and you shouldn't do it. You are literally locking yourself into a flawed way of doing things that is going to cause you problems later. But as you say, there's no law against making bad decisions ¯\_(ツ)_/¯
Thanks for the link and explanation, I'll see with use.With that said:viewtopic.php?t=11134You're misunderstanding the feature. FreeFileSync still treats these file names as different, but matches them as pairs after comparison.
viewtopic.php?t=11134You're misunderstanding the feature. FreeFileSync still treats these file names as different, but matches them as pairs after comparison.
https://stackoverflow.com/questions/23380231/how-to-copy-symbolic-link-file-from-linux-to-windows-and-then-back-to-linux-butIn *nix a symlink is typically just a plain text file with a "symlink" attribute. The file contains the path to the link target. The "symlink" attribute does not exist on Windows.
C:\TMP\BRU\dir_holding_a_symlink>mklink /d spacedout-symLINK C:\TMP\BRU\spacedout
symbolic link created for spacedout-symLINK <<===>> C:\TMP\BRU\spacedout
C:\TMP\BRU\dir_holding_a_symlink>dir
Directory of C:\TMP\BRU\dir_holding_a_symlink
03/20/2024 11:22 AM <DIR> dir1
03/20/2024 11:22 AM <DIR> dir2
03/20/2024 11:16 AM <SYMLINKD> spacedout-symLINK [C:\TMP\BRU\spacedout]
C:\TMP\BRU\dir_holding_a_symlink>