Is your feature request related to a problem? Please describe.
I use symlinks a fair amount locally for various things, and when I sync I get a long list of symlink errors with no clear path to resolution other than not utilizing that particular feature of my file system. This creates a false positive: the logs / status views are filled with complaints about symlinks.
Describe the solution you'd like
I would love the ability to configure Maestral to silence the warnings about symlinks -- treat the file as though it did not exist at all!
Describe alternatives you've considered
-
Removing the warning entirely rather than making it a setting (though I imagine it might be good for users to have to opt into less information).
-
Removing the need for the error at all by writing a maestral-specific symlink solution (e.g. translating the symlink to a .maestral-symlink-{filename} file with a structured format inside, which is then translated to / from Dropbox). This would be great, but I understand it's a bigger lift.
Additional context
I saw this error was added in #581
Is your feature request related to a problem? Please describe.
I use symlinks a fair amount locally for various things, and when I sync I get a long list of symlink errors with no clear path to resolution other than not utilizing that particular feature of my file system. This creates a false positive: the logs / status views are filled with complaints about symlinks.
Describe the solution you'd like
I would love the ability to configure Maestral to silence the warnings about symlinks -- treat the file as though it did not exist at all!
Describe alternatives you've considered
Removing the warning entirely rather than making it a setting (though I imagine it might be good for users to have to opt into less information).
Removing the need for the error at all by writing a maestral-specific symlink solution (e.g. translating the symlink to a .maestral-symlink-{filename} file with a structured format inside, which is then translated to / from Dropbox). This would be great, but I understand it's a bigger lift.
Additional context
I saw this error was added in #581