As mentioned in #59, some parts of this gem conflicts with guard-process since the Process calls aren't made to the global namespace. The pull request in #59 fixes some of these issues, but there was still an issue that appeared when Guard was reloading (for instance after re-evaluating the Guardfile).
As mentioned in #59, some parts of this gem conflicts with guard-process since the Process calls aren't made to the global namespace. The pull request in #59 fixes some of these issues, but there was still an issue that appeared when Guard was reloading (for instance after re-evaluating the Guardfile).