Allow user-based Guardfiles #67

merged 5 commits into from May 28, 2011


None yet

2 participants


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

Joshua Davey... and others added some commits May 24, 2011
Joshua Davey and Veezus Kreist Allow user-based Guardfiles debdecb
Aaron Kalin and Veezus Kreist Conform to project standards add80d2
Aaron Kalin and Veezus Kreist Update README regarding Guardfile location b69aa76

All points conceded:

  • We like to keep to 80 characters per line, which is why we skipped the ternary in guardfile_path
  • We now use tilde instead of ENV['HOME'] - will this satisfy Windows users?
  • We've updated indenting and vertical spacing to match the project

Thanks for the notes, and let us know if there's anything we missed!
Veez and Aaron

Aaron Kalin ... added some commits May 25, 2011
Aaron Kalin and Veezus Kreist Fix guardfile_path spec for Windows support 9928f80
Aaron Kalin and Veezus Kreist Outdent private statement a51afdf
@thibaudgg thibaudgg merged commit a51afdf into guard:master May 28, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment