In my experience, Dropbox responds to all file system I/O, even those outside of the Dropbox folders, strangely. If I'm running, say, npm install or bundle ins

In my experience, Dropbox responds to all file system I/O, even those outside of the Dropbox folders, strangely. If I'm running, say, npm install or bundle install or installing Xcode (or doing anything else I/O heavy), Dropbox starts using a bunch of CPU, proportional to the amount of I/O going on at the time. Note that none of these operations are inside my Dropbox folder. I do believe the FSEvents infrastructure allows you to just watch an individual folder [1], so it shouldn't have to be this way... [1]: https://developer.apple.com/library/mac/documentation/Darwin/Conceptual/FSEvents_ProgGuide/UsingtheFSEventsFramework/UsingtheFSEventsFramework.html https://developer.apple.com/library/mac/documentation/Darwin...