That would be the sensible thing to do.Hm, perhaps that can be a feature request: to ignore trailing spaces with a checkbox in the settings dialog. bgstack15, 21 Mar 2024, 12:56
Search found 13 matches
- 22 Mar 2024, 19:15
- Forum: General Discussion
- Topic: Am I stuck forever with FreeFileSync 13.3?
- Replies: 8
- Views: 1184
Re: Am I stuck forever with FreeFileSync 13.3?
- 22 Mar 2024, 16:52
- Forum: General Discussion
- Topic: Am I stuck forever with FreeFileSync 13.3?
- Replies: 8
- Views: 1184
Re: Am I stuck forever with FreeFileSync 13.3?
Once again, my case is just one example among many. The unintended consequences concern other users.
- 22 Mar 2024, 10:52
- Forum: General Discussion
- Topic: Am I stuck forever with FreeFileSync 13.3?
- Replies: 8
- Views: 1184
Re: Am I stuck forever with FreeFileSync 13.3?
Users don't make mistakes
LOL I see you're one of "those users"
What I meant, more precisely, is that users make mistakes, realize them, correct them, and learn from this process, thus becoming better users. If steps 2 to 4 cannot occur, it's not the user's fault.
Yes, this might be exactly ...
- 21 Mar 2024, 13:33
- Forum: General Discussion
- Topic: Am I stuck forever with FreeFileSync 13.3?
- Replies: 8
- Views: 1184
Re: Am I stuck forever with FreeFileSync 13.3?
So we're not free to call our files and folders whatever we want?
That's so wrong, it's simply unacceptable.
Misguided idea to prevent so-called user errors should remain an option and certainly not be imposed on everyone. Users don't make mistakes, only developers do.
FreeFileSync is a file ...
That's so wrong, it's simply unacceptable.
Misguided idea to prevent so-called user errors should remain an option and certainly not be imposed on everyone. Users don't make mistakes, only developers do.
FreeFileSync is a file ...
- 21 Mar 2024, 11:56
- Forum: General Discussion
- Topic: Am I stuck forever with FreeFileSync 13.3?
- Replies: 8
- Views: 1184
Am I stuck forever with FreeFileSync 13.3?
FreeFileSync 13.4 ignores leading/trailing space when matching file names, according to its release notes. I can hardly believe my eyes.
I constantly use leading spaces in file and folder names to prioritize them at the top of lists on macOS. I'm no coder nor developer and please people, don't ...
I constantly use leading spaces in file and folder names to prioritize them at the top of lists on macOS. I'm no coder nor developer and please people, don't ...
- 03 Aug 2021, 09:27
- Forum: Help
- Topic: FreeFileSync on macOS gives error with folders and files containing the character ≠ in their name
- Replies: 4
- Views: 1373
Re: FreeFileSync on macOS gives error with folders and files containing the character ≠ in their name
For information and in case it helps, the sync that failed because of the ≠ character was between two computers running macOS High Sierra 10.13.6 via the local network.
I also haven't noticed any problems so far with accented characters and other special characters, which I use routinely.
I also haven't noticed any problems so far with accented characters and other special characters, which I use routinely.
- 03 Aug 2021, 00:11
- Forum: Help
- Topic: FreeFileSync on macOS gives error with folders and files containing the character ≠ in their name
- Replies: 4
- Views: 1373
Re: FreeFileSync on macOS gives error with folders and files containing the character ≠ in their name
Have you actually run the sync?(I'll just note that FFS on Windows doesn't look to have any issues with not equal sign.)
.
FFS not-equal-sign.png therube, 02 Aug 2021, 18:35
The comparison with ≠ runs fine as well on macOS.
- 02 Aug 2021, 17:35
- Forum: Help
- Topic: FreeFileSync on macOS gives error with folders and files containing the character ≠ in their name
- Replies: 4
- Views: 1373
FreeFileSync on macOS gives error with folders and files containing the character ≠ in their name
Example:
Cannot read file attributes of "/Volumes/MacBook Pro HD/…/config_EFI_20200525-18h48-idem précédent avec Patches ≠.plist".
ENOENT: No such file or directory [lstat]
Cannot read file attributes of "/Volumes/MacBook Pro HD/…/config_EFI_20200525-18h48-idem précédent avec Patches ≠.plist".
ENOENT: No such file or directory [lstat]
- 31 Jul 2021, 12:41
- Forum: Help
- Topic: FreeFileSync hangs when copying files over 10GB via FireWire on macOS
- Replies: 0
- Views: 327
FreeFileSync hangs when copying files over 10GB via FireWire on macOS
Hi,
I can't get FreeFileSync (11.12) to sync files over 10GB (I think) via FireWire on macOS High Sierra 10.13.6. It hangs indefinitely and I can't stop it or quit. It also hangs the Finder and the only solution is to force reboot.
HTH
I can't get FreeFileSync (11.12) to sync files over 10GB (I think) via FireWire on macOS High Sierra 10.13.6. It hangs indefinitely and I can't stop it or quit. It also hangs the Finder and the only solution is to force reboot.
HTH
- 01 Oct 2019, 11:57
- Forum: Help
- Topic: linux errorcode 24: too many open files
- Replies: 3
- Views: 711
Re: linux errorcode 24: too many open files
Hello,
Have you find the cause of this problem?
I also have the following since a few days and the mentioned post doesn't help (I'm not on Linux but on Mac):
Error Code 24: Too many open files [lstat]
Error Code 24: Too many open files [opendir]
I'm using FreeFileSync to synchronise a selection ...
Have you find the cause of this problem?
I also have the following since a few days and the mentioned post doesn't help (I'm not on Linux but on Mac):
Error Code 24: Too many open files [lstat]
Error Code 24: Too many open files [opendir]
I'm using FreeFileSync to synchronise a selection ...
- 01 Oct 2019, 11:51
- Forum: Help
- Topic: Code 24: Too many open files (Istat)
- Replies: 1
- Views: 500
Re: Code 24: Too many open files (Istat)
Hello ankoe,
Have you find the cause of your problem?
I also have the following since a few days:
Error Code 24: Too many open files [lstat]
Error Code 24: Too many open files [opendir]
I'm using FreeFileSync to synchronise a selection of folders between my desktop and my MacBookPro, both ...
Have you find the cause of your problem?
I also have the following since a few days:
Error Code 24: Too many open files [lstat]
Error Code 24: Too many open files [opendir]
I'm using FreeFileSync to synchronise a selection of folders between my desktop and my MacBookPro, both ...
- 25 Jun 2019, 10:29
- Forum: Help
- Topic: Error Code 1: Operation not permitted [rename]
- Replies: 1
- Views: 254
Re: Error Code 1: Operation not permitted [rename]
I just would like to chime in and add that most of the errors I had months ago have disappeared from recent versions of FreeFileSync.
The last ones remaining are few and all pop up when backing up heavily protected macOS folders such as /Library or /System. They're most likely due to permission ...
The last ones remaining are few and all pop up when backing up heavily protected macOS folders such as /Library or /System. They're most likely due to permission ...
- 21 Mar 2019, 18:54
- Forum: Help
- Topic: Error Code 1: Operation not permitted [rename]
- Replies: 1
- Views: 254
Error Code 1: Operation not permitted [rename]
Hello,
I'm new to freeFileSync (v10.10 under macOS 10.13.6 High Sierra) and I'm experiencing a lot of odd errors.
For instance, when copying folders from an external FW drive to another FW drive, I got dozens of Error Code 1: Operation not permitted [rename]
I don't understand why since I'm ...
I'm new to freeFileSync (v10.10 under macOS 10.13.6 High Sierra) and I'm experiencing a lot of odd errors.
For instance, when copying folders from an external FW drive to another FW drive, I got dozens of Error Code 1: Operation not permitted [rename]
I don't understand why since I'm ...