Closed josephholsten closed 13 years ago
When guard-spork is running, execjs can't access the $CHILD_STATUS ($?) of the javascript runtime it executes.
I'm guessing this has something to do with Guard::Spork::Runner#initialize calling Signal.trap('CHLD', ...)
Guard::Spork::Runner#initialize
Signal.trap('CHLD', ...)
You can try with guard-spork version 0.1.4, Signal trapping came later because some people want to be able to use ruby debugger with Spork (pull #11). Have you an idea to avoid Signal trapping and still have access to ruby debugger?
When guard-spork is running, execjs can't access the $CHILD_STATUS ($?) of the javascript runtime it executes.
I'm guessing this has something to do with
Guard::Spork::Runner#initialize
callingSignal.trap('CHLD', ...)