Closed kassi closed 11 years ago
@xrkhill I let you handle this?
I'll take care of it.
On Thursday, June 20, 2013, Thibaud Guillaume-Gentil wrote:
@xrkhill https://github.com/xrkhill I let you handle this?
— Reply to this email directly or view it on GitHubhttps://github.com/guard/guard-spork/pull/118#issuecomment-19739885 .
I think this is a good suggestion. I'll merge the changes. Thanks for contributing!
Hi, I know you're searching for a maintainer, but this fix is easy and you could quickly think about it.
I always run into this problem: As soon as I edit
Gemfile
, spork will restart itself. Additionally, together with guard-rails, it tries restarts rails as well (as a side effect of restarting spork) which doesn't work because there are gems missing. It always runs into this loop:and continues. Now imho, watching
Gemfile
doesn't make sense since it doesn't affect the app immediately. OnlyGemfile.lock
is important for that. After removingwatch(Gemfile)
I have time to runbundle install
which will, on success, immediately restart sport (and rails and so on).Now you could also add guard-bundler at the top of spork to first create
Gemfile.lock
, which will trigger spork. (However, I don't want that for now).