We're enjoying using Guard as a replacement for our homegrown watchr scripts, but would like to use one Guardfile per user, rather than one per project. This patch will use a local Guardfile first and, if one is not found, then default to a Guardfile in the user's home directory.
We don't have access to a Windows machine to test this one, so we were hoping you'd run it for us. If there's failures, we'd be happy to replicate the environment and test it ourselves, but we didn't see a description of the test environment(s) anywhere.
Veez and Josh
Allow user-based Guardfiles
Conform to project standards
Update README regarding Guardfile location
All points conceded:
Thanks for the notes, and let us know if there's anything we missed!
Veez and Aaron
Fix guardfile_path spec for Windows support
Outdent private statement