Compass watch: possible to configure interval?

[axyl]

Compass watch is great, but it seems to take up quite a bit of CPU power. We're guessing this is because it polls for changes pretty frequently. Is it possible to configure how often it does that? Are there other ways to make it not so CPU-intensive?

[Ryan Frederick]

If you're on a Mac, you can install the rb-fsevent gem which hooks into the OS's file system events system. Install it with `gem install rb-fsevent` and Compass will no longer have to poll. Apparently some of the GUI apps (eg. CodeKit) also use an event system rather than polling.

Unfortunately I don't know about what may be available for Windows or Linux.

[axyl]

I see, we have to use Windows 7 at work though. 

[Ryan Frederick]

I see. I thought I'd Google around to see what I could find. As a non-rubyist it's hard for me to evaluate options, but rb-fchange seems like it *might* help. I don't see existing integration with Compass though, so my guess is that you'd have to write some Ruby code to have rb-fchange run `compass compile`. It also appears to be early in development, with only specific versions of Ruby supported.

[Michael Del Tito]

The guard project might be what you are after:

https://github.com/guard/guard

for compass:

https://github.com/guard/guard-compass

[axyl]

Looks like watch may be deprecated soon in favor of guard. CPU is not a big issue for us, so we'd just wait for the new feature to come out. Thanks for everyone's advice!