Thanks for your fast reply!
After knowing that the script should work correctly, I took a deeper look into my script file, and found a \0, i.e. ASCII value zero, character in it! Seems that the parser stopped at that char and silently ignored the rest of the mask.
May I suggest:
- Would be nice to get some more feedback about how the filemask was parsed. For example if one could get a list of the files to be synced, and the ones excluded, without actually synchronizing? Would make testing cases like this much faster -- actually running the sync can take a very long time.
- And throwing a warning when there is such odd character in the script would be good as well.
Anyways, thanks for a great app, saved the day for me! All other sync solutions I tested were failing miserably...
After knowing that the script should work correctly, I took a deeper look into my script file, and found a \0, i.e. ASCII value zero, character in it! Seems that the parser stopped at that char and silently ignored the rest of the mask.
May I suggest:
- Would be nice to get some more feedback about how the filemask was parsed. For example if one could get a list of the files to be synced, and the ones excluded, without actually synchronizing? Would make testing cases like this much faster -- actually running the sync can take a very long time.
- And throwing a warning when there is such odd character in the script would be good as well.
Anyways, thanks for a great app, saved the day for me! All other sync solutions I tested were failing miserably...