It will not work with files that have already been synced. Note: the IgnoreList is applied to the folder where it is contained and its subfolders. So please do not forget to use “/“ for Mac and unix-based OSes, while for Windows OSes use “\”. When composing a filter consisting of 2 or more components, note that path delimiters are OS-dependent and not universal. For example, a/**/bįilter will ignore folders a/b, a/x/b, a/x/y/b and so on. ![]() \FOO //will not be synced, ignored by FOO\*ĭouble asterisk allows to ignore any amount of subfolders between root folder and target folder. With the above mentioned ignore lines, the following folder structure will behave this way \ABC //wil be syncedĬDE F //will not be synced, ignored by ABC\CDE Fįilename.pdf //will not be synced, ignored by *.pdf This by no means is representative of the masses, but better than not having numbers on the table.Important: on UNIX-based systems use "/" as a path separator. If it matters, I volunteer to tally up the people who care about this enough to type a few sentences here over the past five years. Yes, we cannot have an exhaustive list of everything one would like to ignore, but that shouldn't stop us from trying our best. The solution, however, breaks nothing and is simple just include default ignore lists. I have a few projects of mine corrupted and had to rm -rf. Syncthing by default can and will corrupt. ![]() There is a much stronger point here about usability by default a backup software should never corrupt what is already there. ![]() I bet this number is fairly high, meaning we should not ignore a large portion of our current user base. git is a niche tool but consider this: the number that really matters here is the conditional probability of a syncthing user also using git aka p(uses git | uses syncthing). git/* objects unpredictably - it doesn't happen all the time and doesn't corrupt all the repos just happens sometimes for some repos under some weird race(?) conditions. So far, trying to sync a folder which somehow contained (not directly) a version control repository (e.g.git) corrupts the. Regardless of what platform we're on, we should use the same default excludes for consistency (and because people do share storage devices between systems). local/share/trash is the per-user trash-can for XDG compliant desktop environments on Linux (which is 90% of what people who use X use on Linux). gvfs is found in most people's home directories on Linux when they use most desktop environments other than KDE, and shouldn't be scanned because it covers dynamic access to access transiently connected and non-filesystem items (network filesystems, archives, MTP devices, etc) ![]() I'm not 100% certain what OS it's from, but it looks like ancillary volume metadata (which makes me think it's probably OS X), so it probably shouldn't be synced. fseventsd is something I see a lot on removable media. I've only ever seen this on the C: drive, but I think it shows up on a different drive if there's not enough room on C. $WINDOWS.~BT is a temporary directory used for OS upgrades on Windows (and is often huge if it exists). $RECYCLE.BIN (case insensitive, since newer Windows versions use $Recycle.Bin) is the per-drive recycling bin for Windows
0 Comments
Leave a Reply. |