Edit: Disregard this. Must be a sass bug, because inotifywait works exactly as expected. Thanks for the great work!
Second edit: Actually, maybe it isn’t necessarily a sass bug. It looks like inotifywait is only receiving ATTRIB events when it should be seeing CLOSE_WRITE events. Good enough for our purposes since our local environment scripts are written specifically to run on Docker and adapt to whatever quirks it may have, but if this is a bug then it’s probably worth fixing.
sass --watch should work.
sass --watch does not work.
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
[OK] Moby booted
Docker logs are being collected into /tmp/20160427-185958.tar.gz
Most specific failure is: No error was detected
Your unique id is: 8AB3CD44-FDD7-4ABB-8F39-0831D1416973
Please quote this in all correspondence.
Steps to reproduce the behavior
Run a shell script in a Docker container with a sass --watch command.
Relevant bits from our code:
scssfiles="$(find css -name '*.scss' | grep -v bourbon/ | perl -pe 's/(.*)\.scss/\1/g')" ... for file in $scssfiles ; do sass --watch $file.scss $file.css done