You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes I create a hierarchical structure of empty folders/files with specific names for future work. Currently, Filen does not sync empty files. This frustrates me because when I switch to a second device, I cannot continue working with previously prepared empty files. Also, some programs create backups with empty dotfiles for certain purposes, and such backups may not work properly without these empty files.
For example, Mega syncs empty folders/files by default. It would be great if Filen could sync empty files too.
I think the solution might be to add a toggle "Exclude empty files and folders" to the settings of each sync location. Or perhaps it would be worth considering a more comprehensive solution that would allow for more flexible management of exceptions and filtering by size and so on, in order to achieve results that cannot be obtained through the syntax of .gitignore.
Sometimes I create a hierarchical structure of empty folders/files with specific names for future work. Currently, Filen does not sync empty files. This frustrates me because when I switch to a second device, I cannot continue working with previously prepared empty files. Also, some programs create backups with empty dotfiles for certain purposes, and such backups may not work properly without these empty files.
For example, Mega syncs empty folders/files by default. It would be great if Filen could sync empty files too.
I think the solution might be to add a toggle "Exclude empty files and folders" to the settings of each sync location. Or perhaps it would be worth considering a more comprehensive solution that would allow for more flexible management of exceptions and filtering by size and so on, in order to achieve results that cannot be obtained through the syntax of .gitignore.
The same issue: #95
The text was updated successfully, but these errors were encountered: