Issue: CodeKit thrashing. Feature Request: Option to choose default settings for "Do not compile all"

[builtbybrayne]

I often work on projects with multiple third party libraries, both css (less,sass etc.) or js. There are many more of those files than my own.

Currently the 'do not compile' option is an opt-out, with the default being that all new files are compiled. I'd like a toggle in the preferences so that I switch this behaviour into an opt-in approach. i.e. newly added files are by default ignored and I will manually specify which files should compile.

This may not seem like it should be a problem because theoretically the library files shouldn't change and therefore shouldn't every trigger a compile. In fact, in situations where there are other directory watches and automatic directory/file manipulation going on (which is I think not an unduly unusual edge-case) then the file-changed kernel events will fire and CodeKit will trigger a recompile on every single file - both mine and librarys'. Hence the problem with CodeKit thrashing; it generates a loop where my watch commands respond to some change, CodeKit responds to the effect of my watcher and takes ages to recompile everything, thereby running through into the watcher's next check and triggering a fresh round of watch-modifications/recompiles. By reducing the number of unnecessary file modifications from CodeKit I can apply a reasonable throttle to my watcher to allow CodeKit enough time to compile the files I need, thus stopping the loop.

This may therefore also help (as a workaround) with bugs like the following, as that was the behaviour I found which led me to this desire:

• Infinite refreshing/importing with projects in Dropbox
• Bug: CodeKit not responding / 100% CPU usage

[jrdn91]

Not sure but I do believe that I heard somewhere this will be a feature in the future. Although it was more of a filename matching type of approach if I'm correct in assuming this was said by the codekit developer.