-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Users to Choose To Ignore Empty Files or Not #95
Comments
Sorely needed. |
Yes. This seems almost like a bug to me. It makes most sense that by default all files, empty or not, are synced. And there can be an option to ignore empty files. |
I'm just quietly adding that also empty directories. Not just files. edit: I stand corrected: empty directories do get synced, as of 3.0.34 |
Noting that currently I'm seeing my empty files and directories appear on my Cloud Drive. Edit: I don't know why i wrote that. I see empty directories but not empty files. |
I only see empty directories, not empty files. Both when using
Albeit, only desktop app shows warnings that it has ignored empty files. When using drag-and-drop in the browser, empty directories are not synced either (also without warnings). |
We now have a dedicated forum for feature requests. Please repost it there if possible! :) |
Latest Desktop App under W10. |
Is your feature request related to a problem? Please describe.
During syncing if a folder I noticed that it was saying it ignored a few empty files.
Describe the solution you'd like
Ability to keep empty files. Can toggle off/on.
Describe alternatives you've considered
None
Additional context
This allows the ability to keep the file and folders structure exactly as is. Some work uses them as place holders, flag, etc.
The text was updated successfully, but these errors were encountered: