Full ack. And the best way to get over this for me is to make use of it…
Today I have three .st<something> files:
- . stfolder (was a file, now a folder)
- . stglobal (which has exclusions that are valid for all (my) folders)
- . stignore (which links to .stglobal and has additional exclusions specific to the folder it’s in)
and I sync between Unix and Windows and Mac operating systems.
If I move the .stlobal-file to the .stfolder-folder, the .stignore-file needs to be updated to point to the .stglobal file. That could look like:
#include .stfolder/.stigore
Would that path designator work on an OS platform like Windows? Or do I need to change the .stignore-entry on Windows to #include .stfolder\.stignore?
I’ve tried both but cannot see an error in either case. That could mean it works. It could also mean, Synching doesn’t care. Has anybody tried this? Or simply more insight into the inner workings of the new .stfolder-thing?