Problem with -e option

[adamdziedzic]

Problem with -e option

[marklarr]

@adamdziedzic I'm just now realizing that the -e option is a little misleading. It ignores the group during the reconstruction of your project, meaning that it is essentially deleted, like you said, when your reconstructed (synced) project is copied over your existing project.

The -e flag is really intended for things like Pods and Frameworks -- groups that you don't check into Git. Maybe it's worth rethinking the implementation of the -e flag, though. I don't see any harm in just copying them over to the reconstructed project as-is

[noordawod]

You can grab a copy of a script I wrote to fix few issues with synx, including an option to ignore directories/files altogether:

https://gist.github.com/noordawod/ea1a5fc1fb5654fcba509f6e5862a4eb

[fabb]

I ran into the same issue - imho -e should leave the files where they are.

[fabb]

As a workaround I restore the folders after running synx with git checkout HEAD -- path/to/folder.