Closed mikesmullin closed 12 years ago
Thanks, I'll wait the merge of https://github.com/sporkrb/spork/pull/163
@timcharper it would be great if you can merge it soon. :)
sweet looks like he did it
https://github.com/sporkrb/spork/commit/055b32fb771d6135728c25113851edb9d00cf561
thanks guys. now i won't need my forks.
@mikesmullin can you also just add a little spec for that one please?
@thibaudgg how is this?
Nice, thanks for the specs. I'm wondering if we should not set this option to true by default, don't you think?
well, the way i see it, you might want to see that stuff in the beginning when you're getting spork configured. but once its working, you probably never want to see it again. i'd probably just document the feature in the README.md so they know its an option once they start getting annoyed.
You right, +1 for adding a note to the README and let it at false by default. Can you do that? It would be great. Thanks!
ok how is that?
Great, thanks!
I'm getting invalid option: -q (OptionParser::InvalidOption)
after I try to use this options.
nvm, adding the git repository for the spork gem fixed it.
I'm also getting the error:
invalid option: -q (OptionParser::InvalidOption)
Tried adding the git repo to the gem file, but no luck for me. This is what I have:
gem 'guard-spork', '1.2.0', :git => 'git://github.com/guard/guard-spork.git'
Anyone else getting this problem?
@npearson72 it's because Spork's --quiet option hasn't been released yet (c'mon dudes, it's been five months)
gem 'spork', :git => 'https://github.com/sporkrb/spork.git'
will fix it.
+1
+1 - did this feature fall through the cracks?
Still not, I'm not sure that Spork is maintained anymore.
based on latest guard-spork from today. resolved merge conflicts. see duplicate: https://github.com/guard/guard-spork/pull/58